Required lcel-teacher-eval dataset configuration for langgraph_code_assistant.ipynb is unclear

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.

Example Code
The following code:
# Run eval on base chain
run_id = uuid.uuid4().hex[:4]
project_name = "context-stuffing-no-langgraph"
client.run_on_dataset(
    dataset_name="lcel-teacher-eval",
    llm_or_chain_factory= lambda: (lambda x: x["question"]) | chain_base_case,
    evaluation=evaluation_config,
    project_name=f"{run_id}-{project_name}",
)

Error Message and Stack Trace (if applicable)
{
	"name": "ValueError",
	"message": "Dataset lcel-teacher-eval has no example rows.",
	"stack": "---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
Cell In[23], line 38
     36 run_id = uuid.uuid4().hex[:4]
     37 project_name = \"context-stuffing-with-langgraph\"
---> 38 client.run_on_dataset(
     39     dataset_name=\"lcel-teacher-eval\",
     40     llm_or_chain_factory=model,
     41     evaluation=evaluation_config,
     42     project_name=f\"{run_id}-{project_name}\",
     43 )

File ~/forks/langchain/langgraph/.venv/lib/python3.10/site-packages/langsmith/client.py:3394, in Client.run_on_dataset(self, dataset_name, llm_or_chain_factory, evaluation, concurrency_level, project_name, project_metadata, verbose, tags, input_mapper, revision_id)
   3389 except ImportError:
   3390     raise ImportError(
   3391         \"The client.run_on_dataset function requires the langchain\"
   3392         \"package to run.\
Install with pip install langchain\"
   3393     )
-> 3394 return _run_on_dataset(
   3395     dataset_name=dataset_name,
   3396     llm_or_chain_factory=llm_or_chain_factory,
   3397     concurrency_level=concurrency_level,
   3398     client=self,
   3399     evaluation=evaluation,
   3400     project_name=project_name,
   3401     project_metadata=project_metadata,
   3402     verbose=verbose,
   3403     tags=tags,
   3404     input_mapper=input_mapper,
   3405     revision_id=revision_id,
   3406 )

File ~/forks/langchain/langgraph/.venv/lib/python3.10/site-packages/langchain/smith/evaluation/runner_utils.py:1297, in run_on_dataset(client, dataset_name, llm_or_chain_factory, evaluation, concurrency_level, project_name, project_metadata, verbose, tags, revision_id, **kwargs)
   1289     warn_deprecated(
   1290         \"0.0.305\",
   1291         message=\"The following arguments are deprecated and \"
   (...)
   1294         removal=\"0.0.305\",
   1295     )
   1296 client = client or Client()
-> 1297 container = _DatasetRunContainer.prepare(
   1298     client,
   1299     dataset_name,
   1300     llm_or_chain_factory,
   1301     project_name,
   1302     evaluation,
   1303     tags,
   1304     input_mapper,
   1305     concurrency_level,
   1306     project_metadata=project_metadata,
   1307     revision_id=revision_id,
   1308 )
   1309 if concurrency_level == 0:
   1310     batch_results = [
   1311         _run_llm_or_chain(
   1312             example,
   (...)
   1317         for example, config in zip(container.examples, container.configs)
   1318     ]

File ~/forks/langchain/langgraph/.venv/lib/python3.10/site-packages/langchain/smith/evaluation/runner_utils.py:1125, in _DatasetRunContainer.prepare(cls, client, dataset_name, llm_or_chain_factory, project_name, evaluation, tags, input_mapper, concurrency_level, project_metadata, revision_id)
   1123         project_metadata = {}
   1124     project_metadata.update({\"revision_id\": revision_id})
-> 1125 wrapped_model, project, dataset, examples = _prepare_eval_run(
   1126     client,
   1127     dataset_name,
   1128     llm_or_chain_factory,
   1129     project_name,
   1130     project_metadata=project_metadata,
   1131     tags=tags,
   1132 )
   1133 tags = tags or []
   1134 for k, v in (project.metadata.get(\"git\") or {}).items():

File ~/forks/langchain/langgraph/.venv/lib/python3.10/site-packages/langchain/smith/evaluation/runner_utils.py:971, in _prepare_eval_run(client, dataset_name, llm_or_chain_factory, project_name, project_metadata, tags)
    969 examples = list(client.list_examples(dataset_id=dataset.id))
    970 if not examples:
--> 971     raise ValueError(f\"Dataset {dataset_name} has no example rows.\")
    973 try:
    974     git_info = get_git_info()

ValueError: Dataset lcel-teacher-eval has no example rows."
}

Description

I'm trying to compare the behavior and quality of code assistants both with and without langgraph
the major roadblock has to do with proper configuration of the langsmith dataset
I have had to manually create the lcel-teacher-eval dataset to get around an initial error regarding the dataset not existing

currently I'm getting the error captured above
I don't remember the specific difference in configuration (or dependencies) but at one point I was seeing it write to the personal lcel-teacher-eval dataset consistently.  In this case, the issue was that the input element was being captured as input:input and not input:question.

System Info
System Information
------------------
> OS:  Linux
> OS Version:  #1 SMP Thu Oct 5 21:02:42 UTC 2023
> Python Version:  3.10.13 (main, Feb  7 2024, 15:27:48) [GCC 11.4.0]

Package Information
-------------------
> langchain_core: 0.1.28
> langchain: 0.1.8
> langchain_community: 0.0.21
> langsmith: 0.1.4
> langchain_openai: 0.0.8
> langchainhub: 0.1.14
> langgraph: 0.0.26

Packages not installed (Not Necessarily a Problem)
--------------------------------------------------
The following packages were not found:

> langserve

@rlancemartin - I created an issue for langgraph_code_assistant.ipynb based on our discussion on X.  The issue isn't with LangGraph behavior - it's with the integration with the (personal) LangSmith dataset.  This is a critical usecase - hoping to have a working code example to go with it.

There was a commit midday on Sunday that overwrote some of your changes and changed the behavior.  (It was working better prior to the changes)
https://github.com/langchain-ai/langgraph/commits/main/examples/code_assistant/langgraph_code_assistant.ipynb
LangSmith tracing was configured prior to the change and I was able to add additional items to the dataset from the trace.

@rlancemartin when you have a moment, please:

Move the dataset to langchain-blogs tenant (so we don't accidentally delete at some point)
Publish the dataset (share as public dataset)
Add a client.clone_public_dataset() call with the URL to the top of the notebook to make it usable externally

thanks @hinthornw .  this is a great use of langgraph and langsmith.  appreciate your comments and follow-up

Will do!

Can not emphasize this enough ♥♥♥


Search SQL needs to be looked at for this search.

Describe the bug
A clear and concise description of what the bug is.
All data referenced is Mock Data:
issuing a search like: {{local}}{{contextRoot}}Claim?patient=Patient/17456ca7efe-dfe09119-26e3-4f7f-939e-ece768ca35ad&use=claim&_include=Claim:*
on a very large data set times out.
To Reproduce
Steps to reproduce the behavior:
See Search above
Expected behavior
A clear and concise description of what you expected to happen.
Expect the search to be run in a timely manor.
Additional context
Add any other context about the problem here.
test-24.docx

verified this search and others speeded up. will report on slow queries from the performance bucket after this fix.


String comparison without terminating bytes

Am trying to write a C client. When comparing the draft id at https://github.com/mlichvar/ntp5-exp/blob/main/ntpnode.py#L195 the expected behavior is not clear to me.  Should the length of the string that is compared be the string itself or expanded by 0 to the nearest multiple of 8 octets? The current draft indicates that string terminating characters should not be included so getting the length of the string requires extra operations.

The last commit modified https://github.com/mlichvar/ntp5-exp/blob/main/ntpnode.py#L77 so perhaps the issue hss been resolved, though maybe helpful to indicate in the draft how these string fields should be compared.

The length of the string is given by the length of the extension field in which it is contained. It doesn't have to be divisible by 8 or 4.
I opened https://github.com/ietf-wg-ntp/draft-ietf-ntp-ntpv5/pull/13 to make it more clear.


Continue to use WebSocket?

Not sure if MFCSocket actually needs to use a WebSocket anymore; could probably convert it over to use plain node net libraries. Websocket is a remnant of when MFCSocket was originally designed to work as a browser library.
Not sure if the overhead of using a Websocket instead of a plain old socket is worth worrying about though.
Also, could support two versions, one for node, one for browsers.

@KradekMFC Just some thoughts on that: Their site is gradually modernizing to being mobile-ready/html5/websockets all over the place, and within a year or two (when Flash is truly dead) they may even retire all other communication methods. So a websocket library is definitely needed.
And hey, good news! I discovered the cause of ws >0.7.1 breaking! It's two things! The first is extra validation on MFC's side to make sure our socket connection "comes from a client viewing the main website". All we need to do is fake it by changing the connection statement to pass an "origin" parameter (which is a value describing what website initiated the connection). I tried different values and they're only happy when their domain name is in the origin. Here is what I'm doing in the MFCSocket library now:
new WebSocket( serverUrl, {
			protocolVersion: 13, // rfc6455; current default in the ws library, but we're enforcing it anyway
			origin: 'http://m.myfreecams.com', // pretend that we're connecting to the ws server from the mobile site (this is required, because they validate on the server-side that the Origin header ends in "myfreecams.com")
		});

And you know the list of servers you're retrieving? Make sure you only extract/connect to servers with the "rfc6455" value. They have one or two hybi00 servers, which is not supported by the node-ws client library.
With these two changes it's possible to use ws >=0.7.2!

Actually, here's the code I use to extract only rfc6455 servers:
for( var k in mfcServerConfig.websocket_servers ){
	if( mfcServerConfig.websocket_servers.hasOwnProperty( k ) ){
		if( mfcServerConfig.websocket_servers[k] == 'rfc6455' ){
			_state.serverList.websocketServers.push( k ); // save only the key (the server name, such as "xchat10")
		}
	}
}

Forgot this one:

Not sure if the overhead of using a Websocket instead of a plain old socket is worth worrying about though.

No worries. There's almost no noticeable overhead. The ws library is written in C++ and can deal with thousands of connections at once, each sending loads of messages. A single MFC socket won't slow things down. ;-)

@Temptin I didn't figure there would be much overhead. This was generally just something I was mulling over as I was making some of the other changes.
Thanks for the info with respect to the sockets. I'll update sometime this weekend probably.

@KradekMFC Happy to help! ;-)

For now, sticking with websockets.


Multiple destination setting for new aircraft

Description
When setting up a new aircraft, it's initial destination is set twice, which results in destination stacking warning.
To Reproduce
Steps to reproduce the behavior:

Run the app
Check current log
Scroll down to aircraft creation
See error

Expected behavior
There should be no warnings - resetting the aircrafts should be consistent.

Patched in one of previous PRs,


504 Gateway Time-out

After running the code, the following error occurs when clicking on the link: 504 Gateway Time-out
What can I do about it? Does anyone else have the same problem?

I get the same 504 error. Google colab environment.

facing same issue

I also have the same problem and I don't know the solution


Would help to have a release note somewhere to understand what changed.

The only changed in 2.4 was to integrate custom fields due to Trello's changes in the API.  This is new functionality; no breaking changes.

To answer your question about release notes, they're in the Nuget package and can be viewed either from nuget.org or the Nuget Manager in Visual Studio.

I can look at downgrading the framework version to 4.6. I should have researched the minimum compatibility.

Sorry, I'm getting my libs confused. I had someone comment on my JSON lib about the frameworks. I'll try to apply the same logic here.

It's not obvious to link a pull to a version, maybe just me.

I recognize it's not obvious. The release notes are in the released package. I linked the pull for you in case you wanted to verify that there was nothing else.

Updates on my side:

I overlooked apps without obfuscation. In debug mode, it does compile, but when doing Trello activity, I had another error :
Could not load file or assembly 'System.Threading.Thread, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified

I was in 1.18, in 2.0 there is a breaking change on framework. My app is using framework 4.6, I tried by targeting 4.7.1, but issues with Manatee.
I ended doing a painful rollback to version 1.18 for now, and went back to framework 4.6. I obviously overlooked updating. As it's nuget, I expected things to get smooth. My bad.

I had to do some weird things with my test project, too.  I'll try to resolve those with the next major release (soon).

@mathieuchateau can you move to .Net 4.6.2?  I believe it can consume .Net Standard 1.3.

@gregsdennis I think so. I was just keeping 4.6 to get it working on Vista, if any customer was stuck on it.
I can then even move to 4.7.1, as it works on Windows 7.
I tried 4.7.1 without luck

I'll have to play with it a bit, but I'll get it going.

@mathieuchateau just for kicks, can you try adding
<RestoreProjectStyle>PackageReference</RestoreProjectStyle>

to your project file?
I got the idea from here.

@gregsdennis  already tried, without luck
also tried with also:
<PackageReference Include="Legacy2CPSWorkaround" Version="1.0.0">
      <PrivateAssets>All</PrivateAssets>
    </PackageReference>

I'm going to have to update the json lib first... brb.

@mathieuchateau I've added a RELEASE NOTES.txt file.  I hope this helps.

@mathieuchateau I've migrated that file to https://gregsdennis.github.io/Manatee.Trello/releasenotes/.
This is a much better format both for reading and writing.


video elements fire 'error' event even when successfully assigning to video.src

Can we find a way to intercept and swallow the 'error' event that the  element fires when assigin to the src property?
repro:
videoElement.addEventListener('error', function(event) {
  if (event.target.error.code === window.MediaError.MEDIA_ERR_SRC_NOT_SUPPORTED) {
    console.error(':(');
  }
});
videoElement.addEventListneer('loadedmetadata' function() {
  console.log('success!');
});
videoElement.src = URL.createObjectURL(stream);

The output will be:
:(
success!

I only expect:
success!

I don't see any way to prevent that "error" event. If the user sets a event listener for the "error" event in a <video> element there is little the library/plugin can do to avoid it. In fact, the video element may be later used for rendering a remote video via a HTTP URL, so I prefer not to generate conflict with the element normal behavior.
Said that, it should be documented so I will do it on next days and leave this issue open until done.

Could it be possible to attach the addEventListener for on 'error' when we capture the src attribute change, and then on the event handler remove it and prevent event propagation?

I don't like the idea of overriding native methods, but it may work. Anyhow:

The event handler may be set before the src is attached.
The user may instead use the old-fashion video.onerror = function(error) {} which may require the plugin to also observe the video`s "onerror" property...

It's being coded right now.

Version 1.3.1 published with this improvement.


Add Abstract-CN.md

Please answer these questions before submitting pull request

Why submit this pull request?

[ ] Bug fix

[ ] New feature provided

[ ] Improve performance

Related issues

Bug fix

Bug description.

How to fix?

New feature or improvement

Describe the details and related test reports.

Coverage decreased (-0.004%) to 24.582% when pulling 82f461b955c98af128a2eedc11d06c7ea32b5a7c on xinzhuxiansheng:master into 56d7fe4ed73a1d45647611b9cd32a75682d8e433 on apache:master.

hi,晟哥。"coverage/coveralls" told me that I failed, the "Details" are "UNCOVERED EXISTING LINES :  	apm-sniffer/apm-sdk-plugin/spring-plugins/core-patch/src/main/java/org/apache/skywalking/apm/plugin/spring/patch/AopExpressionMatchInterceptor.java", but I had just amended doc, I checked "Files changed" which is (README_ZH.md,Abstract-CN.md), I don't know why this happened.

Don't worry about coverage.

I'm so sorry that I cliked on the "Update branch" by accident, and I do not know what does that button means.

hi,晟哥，i‘ve fixed some problems and i‘ve committed new doc [eceiver-zipkin/README-CN.md]


Remove web from the CLI command structure

With #247, we no longer need to accommodate for multiple services in the CLI command structure. We only had web for now and can get rid of that.
Tasks

[x] Merge #256 first
[ ] Update code and all directory structures
[ ] Update docs

I have second thoughts on that... While web is the only category we currently have, I'm not sure it's worth the effort to remove it and make life harder if we decide to add it back later.
I could imagine additional core commands related to deployments, testing, etc that live in the CLI itself instead of separate plugins. In that case, we'll need web, as well as deployment, etc. categories.


Reference TS compiler in tests, removing hardcoded VS version

JavaScriptSDK.Tests project is referencing tsc in Exec tasks, assuming it is available in PATH (which it is not, unless installed on the box). I'm referencing TS compiler package and referencing it from packages path
Removing hardcoded VS version, so that solution can be opened and built with VS2015

:shipit:

:shipit: Thanks!


refactor: remove icon font

Description
Since we use svg per icon, we no longer need the CohereIcon font.

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

Project coverage is 75.10%. Comparing base (c80a481) to head (a5ff77c).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #701   +/-   ##
=======================================
  Coverage   75.10%   75.10%
=======================================
  Files         261      261
  Lines       11546    11546
=======================================
  Hits         8672     8672
  Misses       2874     2874

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


"run -on-widows.bat" opens then closes in less than a second without doing anything

https://user-images.githubusercontent.com/75146973/135735711-3c9dfde2-b4c1-41a4-93ac-ea570e00d31e.mp4

Shift + Right click inside that folder. Select Open Command window here or Open PowerShell window here.
in console, Type the following.
> java -jar rhp.jar

Tell me here what it says. Most likely, Java is not available in your system environment variables.


Extension to other huggingface transformer models?

Hi,
I am interested to apply this transformer explainability to other huggingface transformer models such as Swin Transformer and CvT. How can I do so?
Thank you.

Hi @cactusmomo, thanks for your interest!
As of now, the models in this repo are the models we support, expanding to swin Transformers is an interesting and non trivial effort (see previous issues) if you come up with something for that- please share :)


Added interface and trait for enumerable relations.

There have been a lot of discussions regarding enumeration of relations: #7710, #1282. #8402.
Summarized:

Enumerating relationships has its use cases, the number of tickets are a proof of that.
There is no clean implementation for getting all functions that return type X in PHP at this point in time.
There are several "ugly" / suboptimal solutions that could get us a list of relations:

Enumerate getters, call them and check return type, slow probably don't want to do that.
Parse PHPDOC, will work, but can be considered a hack.
Explicitly define names of relationships. Not DRY, requiring me to define my relationships in several places.

This PR is an attempt to prepare Yii2 to support enumerable relationships. When PHP 7 hits, using the return type hint we can easily enumerate getters and check their return type.
Until then, developers that need relation enumeration are forced to create custom implementations which limit the reusability of their code and are very unlikely to be interoperable.
By adding this interface (or merging the interface with ActiveRecordInterface), the framework provides a uniform way for developers to implement enumeration if they need it.

This PR will not break BC for anyone, assuming they are not adding stuff to the yii\db namespace.
If instead the interface is merged with ActiveRecordInterface, it is a minor BC break (people implementing ActiveRecordInterface but not subclassing ActiveRecord will get errors).

--- My own use case for enumerating relations is to (for example) provide a REST API that supports dynamic discovery via HATEOAS.

What's PHP 7 solution?

Checking the return type:
http://php.net/manual/en/reflectionfunctionabstract.getreturntype.php

Anything needed from me for this?

Nope. I need @yiisoft/core-developers opinions on it.

I don't see how this PR makes things better. Relying on method return type is just the same as parsing PHPDoc - it is unreliable.
The only solution for the original issue is using a special DSL for the relation definition methods as It was disscussed at #583.
The problem with the issue is in fact prefix get is too general. There could be a get... method, which returns ActiveQurey, which is not been ment to be a relation, for example:
public function getAllRecordsButThis()
{
    return static::find()->andWhere(['not', ['id' => $this->id]]);
}

Also, this PR proposes a solution only for PHP >= 7.0, while officially minimal version for Yii2 is 5.4. I whould prefer have no built in solution, then the such one.

Well even if we don't include the trait, wouldn't it be good to standardize the interface so developers have something to standardize against?

Anyone else in @yiisoft/core-developers have an opinion on this?

There is no reliable way to support this in the current active record implementation. Adding an interface to the core without an implementation that provides the feature does not make sense to me. Checking the issues I also do not really see a good use case for the need of getting all relations. I am closing this PR as it has not been active for nearly a year now and there is no open issue for it. Thank you for your contribution!


SD-1544 WriteFile#save should not succeed when the src process fails

WriteFile#save would still end up writing the file when the source process halted due to an error, this fixes the function to correctly abort, cleanup and avoid writing the (possibly partial) file.

Current coverage is 78.81%

Merging #1162 into master will decrease coverage by -0.01% as of e3a088c

@@            master   #1162   diff @@
======================================
  Files          164     164
  Stmts         9059    9066     +7
  Branches       258     258
  Methods          0       0
======================================
+ Hit           7141    7145     +4
  Partial          0       0
- Missed        1918    1921     +3

Review entire Coverage Diff as of e3a088c

Powered by Codecov. Updated on successful CI builds.

@jedesah Updated the description of the test you mentioned, any other comments?

Just the response to your earlier comment.

@jedesah Ok, I updated the save test as well.

LGTM!


Question: other editor

Hi. Good work on Go autocomplete. Do you interested in making go autocomplete for Synwrite?
https://sourceforge.net/p/synwrite/wiki/python API/
(job for some $)

Thanks for the feedback. Feel free to email me<EMAIL_ADDRESS>


Instagram stories

Checklist

[X] I'm reporting a broken site
[X] I've verified that I'm running yt-dlp version 2021.12.27. (update instructions)
[X] I've checked that all provided URLs are alive and playable in a browser
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
UK
Description
ERROR: Unsupported URL: https://www.instagram.com/stories/[xxx]
Works fine for Instagram feed posts, just not stories.
Cookies does not help.
Verbose log
yt-dlp https://www.instagram.com/stories/[xxx] --cookies instacookie.txt -Uv
[debug] Command-line config: ['-i', '--format', '((571/272/402/337/315/313/401/336/308/400/271/335/303/299/399/137/248/334/302/298/398/247/136/333/244/135/397/332/243/134/396/331/242/133/395/330/160/394/278)[protocol!=http_dash_segments])+(bestaudio[acodec=opus]/bestaudio[protocol!=http_dash_segments])/best', 'https://www.instagram.com/stories/[xxx]', '--cookies', 'instacookie.txt', '-Uv']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, err utf-8, pref UTF-8
[debug] yt-dlp version 2021.12.27 [6223f67a8] (zip)
[debug] Python version 3.9.0 (CPython 64bit) -<EMAIL_ADDRESS>[debug] exe versions: ffmpeg N-54690-g682990a849-static
[debug] Optional libraries: sqlite
[debug] Proxy map: {}
Latest version: 2021.12.27, Current version: 2021.12.27
yt-dlp is up to date (2021.12.27)
[debug] [generic] Extracting URL: https://www.instagram.com/stories/[xxx]
[generic] [xxx]: Requesting header
WARNING: [generic] Falling back on generic information extractor.
[generic] [xxx]: Downloading webpage
[generic] [xxx]: Extracting information
[debug] Looking for video embeds
ERROR: Unsupported URL: https://www.instagram.com/stories/[xxx]
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/yt_dlp/YoutubeDL.py", line 1353, in wrapper
    return func(self, *args, **kwargs)
  File "/usr/local/bin/youtube-dl/yt_dlp/YoutubeDL.py", line 1423, in __extract_info
    ie_result = ie.extract(url)
  File "/usr/local/bin/youtube-dl/yt_dlp/extractor/common.py", line 599, in extract
    ie_result = self._real_extract(url)
  File "/usr/local/bin/youtube-dl/yt_dlp/extractor/generic.py", line 3829, in _real_extract
    raise UnsupportedError(url)
yt_dlp.utils.UnsupportedError: Unsupported URL: https://www.instagram.com/stories/[xxx]

That page doesn't exist that's why it's failing.

It obviously did exist at the time I opened this ticket. Stories only exist for 24 hours.

You are going to have to provide a URL

I guess you could use highlights like this one that don't disappear:
https://www.instagram.com/stories/highlights/17888807746396621/

Already fixed on master https://github.com/yt-dlp/yt-dlp/commit/dd5e60b15dd720727a0242eec2bd6698cb03b8f2
>yt-dlp -F "https://www.instagram.com/stories/thxriqq/XXX/" --cookies-from-browser edge
[Cookies] Extracting cookies from edge
[Cookies] Extracted 2777 cookies from edge
[instagram:story] XXX: Downloading JSON metadata
[instagram:story] XXX: Downloading JSON metadata
[download] Downloading playlist: XXX
[instagram:story] playlist XXX: Collected 2 videos; downloading 2 of them
[download] Downloading video 1 of 2
[info] Available formats for XXX:
...

Yeah, just checked, it works fine for me too on master.

Already fixed on master dd5e60b
>yt-dlp -F "https://www.instagram.com/stories/XXX/XXX/" --cookies-from-browser edge
[Cookies] Extracting cookies from edge
[Cookies] Extracted 2777 cookies from edge
[instagram:story] XXX: Downloading JSON metadata
[instagram:story] XXX: Downloading JSON metadata
[download] Downloading playlist: XXX
[instagram:story] playlist XXX: Collected 2 videos; downloading 2 of them
[download] Downloading video 1 of 2
[info] Available formats for XXX:
...

Thanks! It has "Unsupported URL" with version 2021.12.27 so do you know when this is going to be pushed to an update?


Run aeneas in CI

This is a straightforward extension of https://github.com/AeneasVerif/charon/pull/155. I thought I had to clean up aeneas tests before we could do that but turns out that no.

What's the workflow now? If by updating Charon I break Aeneas, how do I update Aeneas so that the CI becomes green for Charon?

You fix aeneas normally, and the next charon PR should use that. Unfortunately because of the skip_duplicate_run thing we can't re-run the check by hand I think. It would be nice if we could tell GitHub that this job isn't important


update launch.json to match latest vscode

related to: https://github.com/Microsoft/vscode/issues/3338

done


[DOC] "Download & Get Started" page is missing "Was this page helpful?"

What do you want to do?

[X ] Request a change to existing documentation
[ ] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
The "Download & Get Started" page is missing a "Was this page helpful?" section for giving feedback.
I will provide feedback on that page in a separate issue.
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.

Looks like a good feature request.
Catch All Triage - 1 2 3 4 5

I already implemented this in the documentation repo. We can take the backend implementation as is and add the frontend implementation (UI) to the right-hand panel of the project site.


Unable to start monitor with KnexTimeoutError: Knex: Timeout acquiring a connection.

⚠ Please verify that this bug has NOT been raised before.

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

🛡 Security Policy

[X] I agree to have read this project Security Policy

Description
Startup crash with Trace: KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
👟 Reproduction steps
Start container with Uptime Kuma, log in and wait for data to load on the dashboard. Check logs for errors.
👀 Expected behavior
Dashboard would load, monitor checks would be run, log not full of errors.
😓 Actual Behavior
Dashboards do not load any data, monitor checks are not being run, log is full of errors.
🐻 Uptime-Kuma Version
1.23.7
💻 Operating System and Arch
MikroTik RouterOS 7.11.2
🌐 Browser
Firefox latest
🐋 Docker Version
No response
🟩 NodeJS Version
18.18.2
📝 Relevant log output
Welcome to Uptime Kuma
Your Node.js version: 18.18.2
2023-12-02T07:28:50Z [SERVER] INFO: Welcome to Uptime Kuma
2023-12-02T07:28:50Z [SERVER] INFO: Node Env: production
2023-12-02T07:28:50Z [SERVER] INFO: Inside Container: true
2023-12-02T07:28:50Z [SERVER] INFO: Importing Node libraries
2023-12-02T07:28:50Z [SERVER] INFO: Importing 3rd-party libraries
2023-12-02T07:29:55Z [SERVER] INFO: Creating express and socket.io instance
2023-12-02T07:29:55Z [SERVER] INFO: Server Type: HTTP
2023-12-02T07:29:55Z [SERVER] INFO: Importing this project modules
2023-12-02T07:29:56Z [NOTIFICATION] INFO: Prepare Notification Providers
2023-12-02T07:29:56Z [SERVER] INFO: Version: 1.23.7
2023-12-02T07:29:56Z [DB] INFO: Data Dir: ./data/
2023-12-02T07:29:56Z [SERVER] INFO: Connecting to the Database
2023-12-02T07:29:57Z [DB] INFO: SQLite config:
[ { journal_mode: 'wal' } ]
[ { cache_size: -12000 } ]
2023-12-02T07:29:57Z [DB] INFO: SQLite Version: 3.41.1
2023-12-02T07:29:57Z [SERVER] INFO: Connected
2023-12-02T07:29:57Z [DB] INFO: Your database version: 10
2023-12-02T07:29:57Z [DB] INFO: Latest database version: 10
2023-12-02T07:29:57Z [DB] INFO: Database patch not needed
2023-12-02T07:29:57Z [DB] INFO: Database Patch 2.0 Process
2023-12-02T07:29:57Z [SERVER] INFO: Load JWT secret from database.
2023-12-02T09:29:57+02:00 [SERVER] INFO: Adding route
2023-12-02T09:29:57+02:00 [SERVER] INFO: Adding socket handler
2023-12-02T09:29:57+02:00 [SERVER] INFO: Init the server
2023-12-02T09:29:57+02:00 [SERVER] INFO: Listening on 3001
2023-12-02T09:29:57+02:00 [SERVICES] INFO: Starting nscd
2023-12-02T09:30:07+02:00 [AUTH] INFO: Login by token. IP=<IP_ADDRESS>
2023-12-02T09:30:07+02:00 [AUTH] INFO: Username from JWT: lenno
2023-12-02T09:30:07+02:00 [AUTH] INFO: Successfully logged in user lenno. IP=<IP_ADDRESS>
Trace: KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
    at Client_SQLite3.acquireConnection (/app/node_modules/knex/lib/client.js:312:26)
    at async Runner.ensureConnection (/app/node_modules/knex/lib/execution/runner.js:287:28)
    at async Runner.run (/app/node_modules/knex/lib/execution/runner.js:30:19)
    at async RedBeanNode.normalizeRaw (/app/node_modules/redbean-node/dist/redbean-node.js:572:22)
    at async RedBeanNode.getRow (/app/node_modules/redbean-node/dist/redbean-node.js:558:22)
    at async Monitor.getParent (/app/server/model/monitor.js:1587:16)
    at async Monitor.isParentActive (/app/server/model/monitor.js:1670:24)
    at async Monitor.isParentActive (/app/server/model/monitor.js:1676:30)
    at async Proxy.toJSON (/app/server/model/monitor.js:106:29)
    at async UptimeKumaServer.getMonitorJSONList (/app/server/uptime-kuma-server.js:150:34) {
  sql: '\n' +
    '            SELECT parent.* FROM monitor parent\n' +
    '    \t\tLEFT JOIN monitor child\n' +
    '    \t\t\tON child.parent = parent.id\n' +
    '            WHERE child.id = ?\n' +
    '        ',
  bindings: [ 64 ]
}
    at process.unexpectedErrorHandler (/app/server/server.js:1895:13)
    at process.emit (node:events:517:28)
    at emit (node:internal/process/promises:149:20)
    at processPromiseRejections (node:internal/process/promises:283:27)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:32)
If you keep encountering errors, please report to https://github.com/louislam/uptime-kuma/issues
Trace: KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
    at Client_SQLite3.acquireConnection (/app/node_modules/knex/lib/client.js:312:26)
    at async Runner.ensureConnection (/app/node_modules/knex/lib/execution/runner.js:287:28)
    at async Runner.run (/app/node_modules/knex/lib/execution/runner.js:30:19)
    at async RedBeanNode.findOne (/app/node_modules/redbean-node/dist/redbean-node.js:499:19)
    at async beat (/app/server/model/monitor.js:337:32)
    at async safeBeat (/app/server/model/monitor.js:1026:17) {
  sql: undefined,
  bindings: undefined
}
    at safeBeat (/app/server/model/monitor.js:1028:25)
2023-12-02T09:32:07+02:00 [MONITOR] ERROR: Please report to https://github.com/louislam/uptime-kuma/issues

///--cut--//

2023-12-02T09:32:37+02:00 [MONITOR] ERROR: Please  SUM all duration, also trim off the beat out of time windowreport to https://github.com/louislam/uptime-kuma/issues
2023-12-02T09:32:37+02:00 [MONITOR] INFO: Try to restart the monitor
Trace: KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
    at Client_SQLite3.acquireConnection (/app/node_modules/knex/lib/client.js:312:26)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at process.processTimers (node:internal/timers:509:9)
    at async Runner.ensureConnection (/app/node_modules/knex/lib/execution/runner.js:287:28)
    at async Runner.run (/app/node_modules/knex/lib/execution/runner.js:30:19)
    at async RedBeanNode.findOne (/app/node_modules/redbean-node/dist/redbean-node.js:499:19)
    at async beat (/app/server/model/monitor.js:337:32)
    at async safeBeat (/app/server/model/monitor.js:1026:17) {
  sql: undefined,
  bindings: undefined
}
    at safeBeat (/app/server/model/monitor.js:1028:25)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at process.processTimers (node:internal/timers:509:9)
2023-12-02T09:32:37+02:00 [MONITOR] ERROR: Please report to https://github.com/louislam/uptime-kuma/issues
2023-12-02T09:32:37+02:00 [MONITOR] INFO: Try to restart the monitor

Considering you are using a router, it's likely you are using a USB attached storage? It's likely that the database has gotten too large that the increased IO latency is too much for the application to handle.

That's very strange.
If you have worked with databases before, you can stop the application, and open the database file data.db in any SQLite compatible application (dbeaver, beekeeper, etc). You can then manually delete old rows in the heartbeat table.

Hello, I seem to have a similar problem.
This morning, without having received any particular notification, I saw that all the monitors had a problem during the night, in the docker logs, the line Pending: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? is present on all monitors.
I'm on a VPS running AlmaLinux 8.9 (Midnight Oncilla) with a 4.18.0-513.5.1.el8_9.x86_64 kernel.
Uptime kuma version: 1.23.8 and Docker version 24.0.7, build afdd53b
Regards,

I see a very similar error, running in docker on my Synology NAS:
2023-12-30T12:49:44+01:00 [MONITOR] INFO: Try to restart the monitor
Trace: KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
    at Client_SQLite3.acquireConnection (/app/node_modules/knex/lib/client.js:312:26)
    at async Runner.ensureConnection (/app/node_modules/knex/lib/execution/runner.js:287:28)
    at async Runner.run (/app/node_modules/knex/lib/execution/runner.js:30:19)
    at async RedBeanNode.normalizeRaw (/app/node_modules/redbean-node/dist/redbean-node.js:572:22)
    at async RedBeanNode.getRow (/app/node_modules/redbean-node/dist/redbean-node.js:558:22)
    at async RedBeanNode.getCell (/app/node_modules/redbean-node/dist/redbean-node.js:593:19)
    at async Settings.get (/app/server/settings.js:54:21)
    at async exports.setting (/app/server/util-server.js:610:12)
    at async /app/server/server.js:199:13 {
  sql: 'SELECT `value` FROM setting WHERE `key` = ?  limit ?',
  bindings: [ 'trustProxy', 1 ]
}
    at process.unexpectedErrorHandler (/app/server/server.js:1899:13)
    at process.emit (node:events:517:28)
    at emit (node:internal/process/promises:149:20)
    at processPromiseRejections (node:internal/process/promises:283:27)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:32)
If you keep encountering errors, please report to https://github.com/louislam/uptime-kuma/issues

Piling on: I have also been seeing this issue for over a year when I am moving around the app a lot (looking across monitors, editing the dashboards) but it usually self-resolves after a couple minutes of letting things catch up. Today it has not resolved and lead me to this issue.

We implemented incremental_vacuum in 1.23 which should have mitigated this issue. Can you check if you are running the latest version, and if so, are there items in the logs that indicate the incremental_vacuum task has failed?

@chakflying just confirmed, 1.23.11. I have docker image update monitors, so I would have updated within days to a week from release.

I think the problem is less about vacuum and more that the heartbeat table was huge at >3 million records for a small number of monitors.

What is your retention set to?

@CommanderStorm Took me a few to find that as I'd never changed it. It was set to the default (I assume) of 180 days. I just set it to 14 days just now to hopefully avoid this issue again

Okay. I am assuming your issue is the same @lnagel
We know that lowering retention is not a good solution for the long term, but for 1.23.X that is everything that we can offer as a quick "remedy".
A lot of performance improvements (using aggregated vs non-aggregated tables to store heartbeats, enabling users to choose mariadb as a db-backend, pagination of important events) have been made in v2.0 resolving™ this problem-area.
=> I'm going to close this issue
You can subscribe to our releases and get notified when a new release (such as v2.0-beta.0) gets made.
See https://github.com/louislam/uptime-kuma/pull/4171 for the bugs that need addressing before that can happen.
Meanwhile (the issue is with SQLite not reading data fast enough to keep up):

limit how much retention you have configured
limit yourself to a reasonable amount of monitors (hardware-dependant, no good measure)
don't run on slow disks or disk with high latency like HDDs, SD-cards, USB-Stick attached to a router, ...


[Draft PR] Fix incorrect tuner error message

What does this PR do?

Fixes #15855
Does your PR introduce any breaking changes? If yes, please list them.

Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[x] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you list all the breaking changes introduced by this pull request?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃

FYI, the existing test test_if_lr_finder_callback_already_configured needs to be adjusted because of the changed logic.


error in med to mdpa conversion

Plate.zip
Error:
Traceback (most recent call last):
[Plate.zip](https://github.com/nschloe/meshio/files/3232605/Plate.zip)
[Plate.zip](https://github.com/nschloe/meshio/files/3232606/Plate.zip)
  File "/usr/local/bin/meshio-convert", line 10, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.7/dist-packages/meshio/cli.py", line 39, in main
    write(args.outfile, mesh, file_format=args.output_format)
  File "/usr/local/lib/python3.7/dist-packages/meshio/helpers.py", line 227, in write
    return interface.write(filename, mesh, *args, **_kwargs)
  File "/usr/local/lib/python3.7/dist-packages/meshio/mdpa_io.py", line 560, in write
    _write_data(fh, "NodalData", name, dat, write_binary)
  File "/usr/local/lib/python3.7/dist-packages/meshio/mdpa_io.py", line 450, in _write_data
    fh.write("Begin " + tag + " " + name + "\n\n".encode("utf-8"))
TypeError: can only concatenate str (not "bytes") to str

Thanks for the concise report!

Thanks for the fast fix!!!!


I can't launch it after the last update.

Reminder

[X] I have read the README and searched the existing issues.

Reproduction
(venv) E:\LLaMA-Factory>llamafactory-cli webui
Traceback (most recent call last):
  File "C:\Users\USER\AppData\Local\Programs\Python\Python310\lib\runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "C:\Users\USER\AppData\Local\Programs\Python\Python310\lib\runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "E:\LLaMA-Factory\venv\Scripts\llamafactory-cli.exe\__main__.py", line 4, in <module>
ModuleNotFoundError: No module named 'llmtuner.cli'

Expected behavior
I always started it that way and the webui worked
System Info
python 3.10
transformers  4.40.1
torch 2.3.0+cu121
win 10
Others
Help me solve the problem. Or tell me which command to roll back to the previous version?

pip uninstall llmtuner
pip install -e .


Solving system of PDEs/ODEs

Hello, I was wondering if the code currently supports solving a BVP of the form $L(u) = v,$ where $L$ is some differential operator, $u(x,y), v(x,y) \in \mathbb{R}^2$ and $x$ and $y$ are scalar coordinates.
I tried to modify the example BVP to be trained with a neural network with a vector output, but the functions in conditions.py and solvers.py  assume that the output of the PDE is scalar.
This package is very nicely written, thank you!

Can't you substitute x, y into u, v and create a system of two equations?
Also, it would be great if you can post an MWE for this case.


[AERIE-1734] Use configurable logging in scheduler

Tickets addressed: AERIE-1734
Review: By commit
Merge strategy: Merge (no squash)

Description
Same general approach as for merlin server, but with a lot more bookkeeping.

Deleted CSTNU from the dependencies, freeing up sfl4j
Made log level filtering and output file configuration possible with java system properties in docker-compose.yml.
Changed all instances of System.out.println(...) or e.printStackTrace() to use a slf4j logger.

If you (the reviewer) are feeling up to it, it might be worth checking that I got the intended log levels right when converting from System.out.println. They're all in the "Use slf4j for all scheduler logging" commit. There's a lot of them though, and none of them are likely off by more than one level, so that's up to you.
Verification
I tested output from Javalin and verified that it filtered properly. I was not able to trigger any of the existing error or warning logs in the scheduler package, so instead I put a warning in the constructor of gov.nasa.jpl.aerie.scheduler.ActivityType and verified that it popped out when I ran the test suite. (That warning is gone now of course.)
Documentation
I've updated deployment/Environment.md to reflect this.

I updated a bit of AppConfiguration's javadoc; that's what the force push was for.

Since I haven't really worked with a logger before, I am curious to learn when it's appropriate to use log.error, and when it's appropriate to throw an exception. (Or should we do both?)

My understanding is that exceptions are for when you want to break the usual control flow and delegate error handling to some other code. If you can gracefully handle an error in the same place it is detected/created then there's no need to throw/catch.

FWIW, I'm a fan of this fellow's thoughts on logging.

The key is repeatability. Just like you should be able to reproduce builds and repeat deployments, you should also be able to reproduce execution. If you can replay what happened when a problem manifested itself, you can troubleshoot it. You need to log just enough data to enable you to repeat execution.


Add support for bucket notifications

what

Add support for bucket notifications
Bypass all vars to log storage module

why

To enable log collection

@osterman It did on a hook

/test all

/test all


Vue 3 Composition API reuse in multiple components

Version
3.2.21
Reproduction link
codesandbox.io
Steps to reproduce
Hello, good morning - I use the Composition API reuse method and to reduce the coding of several functions and variables required in common components, I have created a file with the Composition API reuse method, and within each component the required functions and data I called
What is expected?
Suppose we have 5 variables and 5 functions in a Composition API reuse. Well, we may need all of them in one component.
What is actually happening?
I noticed that when I call a Composition API reuse function on any component, all the data and all the functions are called.
I do not need all of them and in each case a different number is needed

This is not a bug report, this is a usage question. Please use chat.vuejs.org for questions.


Allow all containers to be pulled from private registries

Currently most of the containers in the stack can be overridden to be pulled from a private registry, except for kubegres-controller-manager.
It would be great if the registry address for both kubegres-controller-manager and manager were exposed in the values.yaml. Along with this it would be great to have imagePullSecrets exposed as these exist in a different namespace to the rest of the containers in the stack.

I'd be interested to know what your use case is here... we are currently looking into running ACS on edge systems isolated from the Internet, and we have had success using Harbor as a pull-through cache along with using k3s' private registries configuration to configure machines to pull images through the cache. But obviously this requires some part of the network has Internet access.

The use case is a factory environment with no internet connection. Our images are currently in a private registry and require authentication to retrieve.
If we wanted to remove the need to authenticate we'd need to setup another registry with just the Factory+ containers. K3's private registry configuration would work but we don't have the option to make modifications to the cluster at this point.

I believe this is now resolved with #98, #100, #113 and #114. If there are still issues please feel free to reopen.

Awesome, thanks @amrc-benmorrow!


IListener and IRadio purge

Removes IRadio, IListen and separates radios and listening logic.
New events:

RadioReceive & RadioReceiveAttempt
Listen & ListenAttempt

New Components:

ActiveListener & ActiveRadio. These get added/enabled by other radio or listening related systems.
RadioMicrophone & RadioSpeaker (replaces HandHeldRadio)
WearingHeadset (used for event subscriptions to relay chat messages to the headset)

Significantly modifies the components added in #11640 and #11449.

In particular, the voice recorder has a new verb, admin logs, and different pop-ups

In Future:

SurveillanceCameraMicrophoneComponent should probably be merged with RadioMicrophoneComponent using some radio frequency unique to that broadcast?
I guess eventually the radio system should use device nets? This doesn't do that but should hopefully be easier to convert after this.

In Future:

The only basic thing missing is a way for entities to use themselves as a radio to speak over. I was looking at InnateRadio this weekend for a possible PR after some guy pinged me in a contribution help channel about adding a headset slot to an entity that really shouldn't have one just so it could talk on radio.

The only basic thing missing is a way for entities to use themselves as a radio to speak over.

It should be pretty straightforward to add an an intrinsic radio / microphone component


Automation not working with (L)ocal events

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.50.0 (And also 0.49.0)
Python release (python3 --version):
Python 3.6.1
Component/platform:
My own component
Description of problem:
Automation is not triggering on event specified.
Expected:
The automation should trigger, it does trigger when i manually trigger the event from the UI with following payload : {“id”:“1”,“button”:“1002”} and the type beeing : dcz_event
Problem-relevant configuration.yaml entries and steps to reproduce:
- alias: "Trigger based on event"
  initial_state: true
  trigger:
    platform: event
    event_type: dcz_event
    event_data:
      id: "1"
      button: "1002"
  action:
    service: notify.notify
    data:
      message: An event from dcz

Additional info:
This does not trigger automation (event fired from the custom component)
2017-07-30 22:15:10 INFO (MainThread) [homeassistant.core] Bus:Handling <Event dcz_event[L]: id=1, button=1002>
and this triggers (made locally with the HASS UI in events)
2017-07-30 22:15:15 INFO (MainThread) [homeassistant.core] Bus:Handling <Event dcz_event[R]: id=1, button=1002>

I have fixed the issue to set the eventorigin to remote, i am not sure that is the correct way but now it works


ImportError: cannot import name spaces with python 2.7, TF 1.5

In the https://github.com/tensorflow/tensor2tensor/blob/master/tensor2tensor/notebooks/hello_t2t.ipynb  with current pip distribution following code:
!pip install -q 'tensor2tensor==1.4.1' 'tensorflow==1.5.0rc0'
from tensor2tensor import problems

Produces:
ImportErrorTraceback (most recent call last)
<ipython-input-2-03b51d1582cc> in <module>()
      6
      7 from tensor2tensor import models
----> 8 from tensor2tensor import problems
      9 from tensor2tensor.layers import common_layers
     10 from tensor2tensor.tpu import tpu_trainer_lib

/usr/local/lib/python2.7/dist-packages/tensor2tensor/problems.py in <module>()
     25 # Dependency imports
     26
---> 27 from tensor2tensor.data_generators import all_problems  # pylint: disable=unused-import
     28 from tensor2tensor.utils import registry
     29

/usr/local/lib/python2.7/dist-packages/tensor2tensor/data_generators/all_problems.py in <module>()
     26 from tensor2tensor.data_generators import cnn_dailymail
     27 from tensor2tensor.data_generators import desc2code
---> 28 from tensor2tensor.data_generators import gym
     29 from tensor2tensor.data_generators import ice_parsing
     30 from tensor2tensor.data_generators import image

/usr/local/lib/python2.7/dist-packages/tensor2tensor/data_generators/gym.py in <module>()
     24 # Dependency imports
     25
---> 26 import gym
     27
     28 from tensor2tensor.data_generators import generator_utils

/usr/local/lib/python2.7/dist-packages/gym/__init__.pyc in <module>()
     10 from gym.core import Env, Space, Wrapper, ObservationWrapper, ActionWrapper, RewardWrapper
     11 from gym.envs import make, spec
---> 12 from gym import wrappers, spaces, logger
     13
     14 def undo_logger_setup():

/usr/local/lib/python2.7/dist-packages/gym/spaces/__init__.py in <module>()
----> 1 from gym.spaces.box import Box
      2 from gym.spaces.discrete import Discrete
      3 from gym.spaces.multi_discrete import MultiDiscrete
      4 from gym.spaces.multi_binary import MultiBinary
      5 from gym.spaces.prng import seed, np_random

/usr/local/lib/python2.7/dist-packages/gym/spaces/box.py in <module>()
      1 import numpy as np
----> 2 from gym import Space, spaces, logger
      3
      4 class Box(Space):
      5     """

ImportError: cannot import name spaces

---------------------------------------------------------------------------
NOTE: If your import is failing due to a missing package, you can
manually install dependencies using either !pip or !apt.

To view examples of installing some common dependencies, click the
"Open Examples" button below.
---------------------------------------------------------------------------

Yes, we've updated the notebook (on GitHub - should go out to the colab site shortly) and the gym dep to a version that wasn't broken.


Building Summary pages with many items is slow & resource intensive

We haven't narrowed this down very precisely, but can consistently replicate a project with ~50 data files causing a 504 on production . Other projects with many data files are also quite slow to build the summary page.

Probably something to do with the data project zip file. For this page, the server will try to assemble a zip file for users to download, which can be resource intensive if there are 50 files.

What happens if you try to "download data project" on QDR?

It's giant -- 1.7BG -- but downloads without any noticeable impact on the site (which has a very robust machine on the server, of course, though)

Some options we can explore:

scale AnnoRep vertically (increase the memory capacity of AnnoRep server)
Allow users to download the data project zip on the client-side, but I need to break my rule of never using the user's API token on the client side. AnnoRep server does all API calls and never exposes the API token in client-side code.
Remove download data project button

I think we can remove the download data project button. No one asked about this and the people who did were confused by what they got (expecting an annotated manuscript).
For this functionality

we offer the annotation download
people can download the files from DV

so this really just turns 1 step into 2.

@nniiicc would you chime in on this -- I think you already liked the idea of a download, so maybe I'm not thinking of usecases

I am in favor of removing the download data project button - I agree with your reasoning above

Sounds good, I will remove the button


Localnet ux e2e test idempotent vlan creation

What this PR does and why is it needed

Which issue(s) this PR fixes

Fixes #
Special notes for reviewers

How to verify it

Details to documentation updates

Description for the changelog

Does this PR introduce a user-facing change?

/cc @RamLavi


SAA-1985: Update allocation prisoner status to ACTIVE when changing start date to today

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

Project coverage is 84.10%. Comparing base (03ea34a) to head (9288d53).

Additional details and impacted files
@@            Coverage Diff            @@
##               main    #1022   +/-   ##
=========================================
  Coverage     84.10%   84.10%
- Complexity     3662     3663    +1
=========================================
  Files           381      381
  Lines         12352    12353    +1
  Branches       1062     1063    +1
=========================================
+ Hits          10389    10390    +1
  Misses         1470     1470
  Partials        493      493

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


Rancher do not take automatic snapshots of Elemental RKE2 cluster

Rancher version: ?
RKE2 cluster version: v1.25.9+rke2r1
Rancher configured to take automatic snapshots: snapshots for elemental RKE2 clusters are not there ("Restore Snapshot" from the Cluster Management Rancher UI doesn't show any available snapshot).
Note that:

elemental K3s  v1.25.9 clusters have regular snapshots
not elemental RKE2   v1.25.9clusters have regular snapshots

no longer relevant


Get-ForensicTimeline Amcache Error on Windows 7

Hello,
When trying to run Get-ForensicTimeline on a Windows 7 machine I get the error:

Exception calling "GetInstances" with "1" argument(s): "The Amcache hive is only available on Windows 8 and newer Operating Systems."

Is this cmdlet only available on Windows 8 and newer OS's? Is there a way to take the Amcache hive parser out?

Thank you for bringing this to my attention. The Amcache Hive is first
present on Windows 8 and thus would fail on Windows 7, but the error should
not be a terminating error (especially on Windows 7) so you can complete
your timeline. If possible, can you file an issue with the project as that
will let me better track my progress on fixing this issue.
Thanks,
Jared
On Wed, Jul 26, 2017 at 9:25 AM, johnpaulglab<EMAIL_ADDRESS>wrote:

Hello,
When trying to run Get-ForensicTimeline on a Windows 7 machine I get the
error:
Exception calling "GetInstances" with "1" argument(s): "The Amcache hive
is only available on Windows 8 and newer Operating Systems."
Is this cmdlet only available on Windows 8 and newer OS's? Is there a way
to take the Amcache hive parser out?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Invoke-IR/PowerForensics/issues/149, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AMqcAkvsVmk9sk_LXNkL4JYabb693bTwks5sR2iFgaJpZM4OkKuS
.


fix(packagejson):fix typo in package.json

fix(packagejson):fix typo in package.json

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


js example as default in readme

If popularity of this library is desired, I would use javascript (latest release is probably fine) for the initial/first/default example of usage (and correspondingly forego unnecessary complications like export default Vue.extend({})). I would also include all possible implementation approaches (e.g. I just had to look up props for SelectMulti because I was not able to use v-model and luckily saw that values is a prop). If you want to additionally show one in typescript then I would call it out as a ts example.
Further, I would reduce the indents to 2 spaces in the examples.

Excellent points all around. We definitely need a way that's a quicker onboarding process, whether we do that through a Storybook docs page, or a standalone VuePress thing or something. And the points are super well-taken re: formatting of examples.

Hi @RED143 - I'd like us to do a couple things for this issue:

Let's switch the examples in the README to be as simple as possible - so that would be showing a JS, rather than TS, component - likely no method handlers needed, just v-model. And probably having nothing about custom SCSS, just show importing the mixins & initializing them w/ no args

Then, let's get to work on improving our onboarding site, so that if someone opens
a) I'd like an intro page to load first, and it can be super similar to this one that another library put together using Storybook MDX: https://reaviz.io/?path=/story/docs-intro--page (code is here: https://github.com/reaviz/reaviz/blob/master/docs/getting-started/Intro.story.mdx)
b) and then in addition to our SelectSingle.stories and SelectMulti.stories, which can stay exactly the way they are & be the source of truth for "here's all the things they can do", we can probably create something like
CommonUseCases.stories.mdx and StylingOptions.stories.mdx - these can be done in a follow-up ticket, but I want us to be thinking about how we'd document, more simply "here's a few common things you might need to do w/ SelectMulti and "here's how you pass in custom styling variables"

So for this particular issue, let's just worry about 1 and 2a, then we can discuss & work on 2b some other time

Awesome work by @RED143 on this, in #69!
Closing ✅


Damaged Blue Moon Items Missing Clue Icon

Fully repaired blue moon equipment properly has its master difficulty icon over it, but as soon as it gets damaged it does not.

Thank you for reporting this issue! 🚀
A patch has been implemented and is currently under review by RuneLite.
You can track the current status here: https://github.com/runelite/plugin-hub/pull/6939


Manga347 factory change

Source information
Manga347 v1.4.35
Source language
English
Steps to reproduce
1.install extension
2.try to load anything from the extension
Expected behavior
Manga / comics should load like normal
Actual behavior
Doesn't load anything
Tachiyomi version
All
Android version
11
Other details
This is happening due to a factory change, they used to use madara , but they changed it to something else few months ago (probably a year ago)
I have yet to identify the factory or website/wordpress theme
Acknowledgements

[x] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.2.
[X] I have updated all installed extensions.
[x] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

It's using the MangaReader theme, like manhuagold.

Theme: MangaReader => https://github.com/keiyoushi/extensions-source/blob/1b93df87e057a8a69ddb75f3afcf445e915aca7a/lib-multisrc/mangareader/src/eu/kanade/tachiyomi/multisrc/mangareader/MangaReader.kt


Parse methods

Methods has column named Parameters
Example: https://core.telegram.org/bots/api#answerinlinequery
Depends on #1

I think #18 fixed this issue, right? What's missing is proper output for methods. One possibility would be what @sergeysova said here: https://github.com/sergeysova/telegram-typings/pull/18#issuecomment-387486772
Working on this should not happen before the refactoring of builders, from classes to functions, if I understood this correctly: https://github.com/sergeysova/telegram-typings/pull/18#issuecomment-387512909


reactivemongo 0.12.1 breaks projects using play 2.5.x

reactivemongo 0.12.1 introduces a dependency on play-iteratees 2.6.1, where version 0.12.0 only required 2.3.10, and thus breaking play at runtime when Streams are used:

java.lang.NoClassDefFoundError: play/api/libs/concurrent/StateMachine
java.lang.NoClassDefFoundError: play/api/libs/streams/impl/EnumeratorSubscription

I tried pinning the play-iteratees module to 2.5.10:

dependencyOverrides += "com.typesafe.play" %% "play-iteratees" % "2.5.10"

Now I can use Streams again, and also reactivemongo seems to be working fine.
Is there a specific reason why the dependency was bumped to 2.6.1 in a minor release of reactivemongo?

Hi,
As indicated in the compatibility nodes, ReactiveMongo is compatible with required Play libraries from "2.3.13 to 2.5.9" (now up to 2.6.1).
If you want to use the latest ReactiveMongo but not the latest Play libraries, you can use standard SBT eviction (what's done by default with the Play module).
("org.reactivemongo" %% "reactivemongo" % buildVersion).exclude("com.typesafe.play", "*")

As indicated, the MailingList is the "place to ask questions or get help" (not this issue tracker).

Best regards


Add support for rendering chat transcript system messages

Add the design and rendering for system messages that come from chat transcript only. This works for both live chat transcript and secure conversations chat transcript, because they both use the same ChatView. Nothing has been done to render system messages that come from web socket yet to keep the commit small.
MOB-2040

!squash

!merge


PowerShell comment syntax highlight is not correct.

We have written the needed data into your clipboa
Issue Type: Bug
The highlight syntax for comments is wrong for PowerShell files.
EG.
.\procedure.ps1 `
   -arg1 $variableforarg1 ` #this syntax highlighting should not resemble a comment
   -arg2 $variableforarg2 ` <#this syntax highlight should not resemble a comment because it's invalid to add a comment here #>
   -arg3 $variableforarg3 <#this syntax higlight should be correct#>`
   -arg4 $variableforarg4

The example above shows that the "arg1" and "arg2" have incorrect comments and should not by syntax higlighted as comments.
For me saddly as a beginner powershell user this was an issue when trying to deploy :(. Just want to make that you have a visual cues when using this and not commit a faulty powershell script in production like me.
P.S. if you use the PowerShell ISE it will syntax highlight correctly.
VS Code version: Code 1.31.1 (1b8e8302e405050205e69b59abb3559592bb9e60, 2019-02-12T02:20:54.427Z)
OS version: Windows_NT x64 10.0.16299

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (8 x 3408)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
31.89GB (15.24GB free)

Process Argv
C:\Users\stem\Documents\Repos\track-system\TrackServices\Database\schema\58_upgrade_from_v57_to_v58.sql

Screen Reader
no

VM
0%

Extensions (7)

Extension
Author (truncated)
Version

EditorConfig
Edi
0.13.0

gc-excelviewer
Gra
2.1.29

prettify-json
moh
0.0.3

mssql
ms-
1.4.0

csharp
ms-
1.17.1

PowerShell
ms-
1.11.0

vetur
oct
0.16.2

rd because it was too large to send. Please paste.

@stefanita-mitran I can reproduce this, but it also occurs in PowerShell ISE. I'll move this issue to the owners of the PowerShell grammar.

This issue was moved to PowerShell/EditorSyntax#161


Report config push failures as Events

What this PR does / why we need it:
Adds tag information indicating the Kubernetes resource that resulted in a Kong resource.
Adds parent information to Services, to indicate which route initially added them. Mostly for multi-service backends, which we cannot tag with a single Kubernetes Service and need to tag with whatever GWAPI route added them.
Handles and uses the Kong 3.2 flattened error response for DB-less pushes.
Generates Events associated with problem resources when a DB-less push fails.
Which issue this PR fixes:
Best-effort solution for FTI-4350. Although we cannot reject such failures up front, we can make their cause more accessible than the status quo (controller logs mention the Kong entity at fault, but not the Kubernetes resources). Users can query events by type and see the Kubernetes resource in the Event data.
Special notes for your reviewer:
WIP commits left as-is. This will eventually be squashed, but the history is too long and complicated to rebase into a more cohesive set of commits. The individual commits may be somewhat more useful to understand history than squashing up front. Apologies for the size, the original mandate was to produce a working PoC up front, so the issue was not broken into smaller chunks.
The addition of Kubernetes resource tags broke a large number of unit tests that want to compare complete objects. The tag contents are irrelevant to those tests, but break Equal(). My updates to unit tests either null out the tags before comparison or add the tags to the expected objects, depending on which was easier for the individual test. This (and similar broad changes in the past) requiring so many changes suggests we should amend these tests to instead compare relevant fields instead of complete objects, but reviewing which fields are relevant and refactoring all tests is a large effort. Depending on the unit test, not all would add useful tags anyway (since they're not starting from a complete Kubernetes resource).
Integration tests require running against kong/kong:master-alpine to check this functionality, as 3.2 is unreleased.
event_generation_manual.txt is a local run. https://github.com/rainest/kubernetes-ingress-controller/pull/189 uses a modified CI job to run this elsewhere (the nightly test job was already a bit broken and, I expect, now much more broken due to lack of updates to keep up with the main CI test job).
PR Readiness Checklist:
Complete these before marking the PR as ready to review:

[x] the CHANGELOG.md release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR

https://github.com/Kong/kubernetes-ingress-controller/pull/3486 broke the ability to test against arbitrary versions, so local integration testing to confirm positive behavior on unreleased Kong images requires:
KONG_TEST_CLUSTER=kind:kind TEST_KONG_IMAGE=kong/kong TEST_KONG_TAG=master-alpine GOFLAGS="-tags=integration_tests" dlv test ./test/integration -- -test.v -test.run TestConfigErrorEventGeneration

diff --git a/test/integration/suite_test.go b/test/integration/suite_test.go
index 00c116b2..6f7343ba 100644
--- a/test/integration/suite_test.go
+++ b/test/integration/suite_test.go
@@ -65,7 +65,7 @@ func TestMain(m *testing.M) {
        // - rely on a mechanism in ktf that will always, by default return the newest
        //   GW image
        // Related issue: https://github.com/Kong/kubernetes-testing-framework/issues/542
-       kongbuilder.WithProxyImage("kong/kong-gateway", "<IP_ADDRESS>-alpine")
+       // kongbuilder.WithProxyImage("kong/kong-gateway", "<IP_ADDRESS>-alpine")
        kongAddon := kongbuilder.Build()
        builder := environments.NewBuilder().WithAddons(kongAddon)

Figure the old nightly test label is in need of a general update to catch up to the rest of CI, so not trying that yet.

#3486 broke the ability to test against arbitrary versions, so local integration testing to confirm positive behavior on unreleased Kong images requires:
KONG_TEST_CLUSTER=kind:kind TEST_KONG_IMAGE=kong/kong TEST_KONG_TAG=master-alpine GOFLAGS="-tags=integration_tests" dlv test ./test/integration -- -test.v -test.run TestConfigErrorEventGeneration

diff --git a/test/integration/suite_test.go b/test/integration/suite_test.go
index 00c116b2..6f7343ba 100644
--- a/test/integration/suite_test.go
+++ b/test/integration/suite_test.go
@@ -65,7 +65,7 @@ func TestMain(m *testing.M) {
        // - rely on a mechanism in ktf that will always, by default return the newest
        //   GW image
        // Related issue: https://github.com/Kong/kubernetes-testing-framework/issues/542
-       kongbuilder.WithProxyImage("kong/kong-gateway", "<IP_ADDRESS>-alpine")
+       // kongbuilder.WithProxyImage("kong/kong-gateway", "<IP_ADDRESS>-alpine")
        kongAddon := kongbuilder.Build()
        builder := environments.NewBuilder().WithAddons(kongAddon)

Figure the old nightly test label-triggered workflow is in need of a general update to catch up to the rest of CI, so not trying that yet. Probably easiest for now to do a manual dispatch run that runs integration and overrides the Kong image.

This should fix it: #3508

https://github.com/rainest/kubernetes-ingress-controller/actions/runs/4148511218/jobs/7176623721 from fork run https://github.com/rainest/kubernetes-ingress-controller/pull/193 is this against current Kong master.
I was trying to think of a way to make the master image runs conditional (we can either include or exclude them via labels on PRs), but between limitations in Actions and our current matrix system I'm not sure we can. My attempts do run it against latest master, but they always do so. Skipping that without the appropriate label didn't work as I'd hoped, and even if it did I think the matrix means it'd do an extra test run, since it should skip the image override step (it's not even doing this), but that would then result in it still running the matrix entry with the standard image. Ideally it'd not run the extra job at all if it's unnecessary.

@randmonkey

LGTM in general, but I want to know that what happens if POST /config error happened in the following situations:
Kong version <= 3.1
failed to connect to kong admin API

Nothing new. This unmarshals errors from POST /config into a struct that has an omit_empty field for the new flattened_errors field, so if that's not present (either because older Kong versions don't have it or because it's some other class of error), the struct field is empty the code that checks if there are ResourceErrors to process sees none and skips that processing. We then proceed with the error handling we already had (logging a failure and returning an error back up through the sync loop).


Add functionality related to Origin CA root certificates

Description
This PR introduces the ability to:

retrieve the Cloudflare Origin CA Root certificate(s) using this library
print the Origin CA root certificate(s) via e.g. flarectl origin-ca-root-cert --algorithm rsa

See https://github.com/cloudflare/terraform-provider-cloudflare/issues/1096#issuecomment-875302579 for additional information.
Has your change been tested?
Tests have been added as well as explicit comment regarding testing the live endpoints. Unfortunately the Origin CA root certificates are not exposed by Cloudflare on a fixed/API endpoint (as per IPs) so the current solution is brittle as the URLs in use may change over time (which originally led to https://github.com/cloudflare/terraform-provider-cloudflare/issues/1096 being raised).
Types of changes
What sort of change does your code introduce/modify?

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

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

looks great! thank you @onematchfox !


Certificate Issues with v2.9 (BadCertificateRevocationUnknown)

After upgrading to Version 2.9.0 we encounter some certificate issues (see stack trace below). In the past (while using v2.8.4) we were using the command line options:
"--pf=/mount/opcpublishermodule.settings.json",
"--aa",
"--tm",
"--RejectUnknownRevocationStatus=false",
"--mq=100",
"--batchsize=2",
"--heartbeatinterval=15",
"--iothubprotocol=AmqpOverTcp",
"PkiRootPath=/mount/pki"
Is it possible that the CLI command ""--RejectUnknownRevocationStatus=false" is not supported anymore?
Additionally to the stack trace shown below we get the following error message:
Option --RejectUnknownRevocationStatus=false wrong or not supported, please use -h option to get all the supported options.

The certificates are structured like this: https://reference.opcfoundation.org/v104/GDS/docs/F.1/
Stack trace:
[09:50:44.5132] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaStack[512]
      Imported the PFX private key for [***].
[09:50:44.5530] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaClientManager[0]
      Own certificate Subject '***, CN=***, OU=**, O=**, L=**, C=**' (Thumbprint: ***) loaded.
[09:50:44.5569] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaStack[0]
      Checking application instance certificate.
[09:50:44.6482] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaStack[512]
      Imported the PFX private key for [***].
[09:50:44.6495] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaStack[0]
      Check certificate: [***, CN=***, OU=**, O=**, L=**, C=**] [***]
[09:50:44.6522] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaStack[0]
      Check application instance certificate. [***, CN=***, OU=**, O=**, L=**, C=**] [***]
[09:50:44.9421] warn: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaStack[0]
      Certificate Validation failed. Reason=BadCertificateRevocationUnknown. [***, CN=***, OU=**, O=**, L=**, C=**] [***]
[09:50:44.9456] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaStack[0]
      Error validating certificate. Exception: Object reference not set to an instance of an object.. Use certificate anyway?
[09:50:44.9494] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaClientManager[0]
      Error The certificate with subject ***, CN=***, OU=**, O=**, L=**, C=** in the configuration is invalid.
       Please update or delete the certificate from this location:
       /mount/pki/own
       while configuring OPC UA stack - retry...

[09:50:44.9497] dbug: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaClientManager[0]
      Detailed error while configuring OPC UA stack.
      Opc.Ua.ServiceResultException: The certificate with subject ***, CN=***, OU=**, O=**, L=**, C=** in the configuration is invalid.
       Please update or delete the certificate from this location:
       /mount/pki/own

         at Opc.Ua.Configuration.ApplicationInstance.CheckApplicationInstanceCertificate(Boolean silent, UInt16 minimumKeySize, UInt16 lifeTimeInMonths)
         at Azure.IIoT.OpcUa.Publisher.Stack.OpcUaClientOptionsEx.BuildApplicationConfigurationAsync(OpcUaClientOptions options, String identity, CertificateValidationEventHandler handler, ILogger logger) in /home/vsts/work/1/s/src/Azure
.IIoT.OpcUa.Publisher/src/Stack/Extensions/OpcUaClientOptionsEx.cs:line 103

Thanks for reporting this bug, it is a regression of #1777 and caused by the fact that this environment variable was never exposed in the command line, and we only tested the command line options.  Is end of August ok for a fix?

Thanks for your quick answer and your support! Would a pull request from my side significantly speed up this process? If I find some time to look into this, I might be able to support.

Thank you for the offer @delema98, the fix has been integrated as part of the latest snapshot and will be part of 2.9.1, likely mid to end of August.  If you want to test you can publish a docker image from main, and run that one instead of the official one that will be released.


Update star-citizen: 2.0.5 -> 2.0.6

Bump launcher version to 2.0.6

Add work around for java script error

fixes #206

@damccull can you test if this fixes your issue?

@damccull can you test if this fixes your issue?

Yes, I would love to. How do I target this PR to install this version as a test? I'm still learning nixos, and using a flake. Do I just set the input to github and point at this PR specifically?

@damccull change the nix-gaming input url to github:LovingMelody/nix-gaming/update-star-citizen, and rebuild.

Force push changes:

Updated dll overrides to prevent wine from creating desktop icons
Set WINEDEBUG=-all to reduce wine debug messages

Updated packaged to use a cleaner work around. I have tested with systemd-run --user -d -- nix run .\#star-citizen to ensure the issue isnt present still.

I have changed to the repo you mentioned, and even rebooted. Still, typing star-citizen in the terminal will launch it fine but I get the same issue when clicking the shortcut in the apps menu.

@damccull change the nix-gaming input url to github:LovingMelody/nix-gaming/update-star-citizen, and rebuild.

What desktop environment are you using?

Good question that I hadn't considered. It is the default that NixOS seems to use. Gnome on Wayland I believe.
Thanks for being patient with me. I'm familiar with Linux in a server context but I'm still adjusting to 20+ years of Windows use for a desktop environment.

Hmm, it should be using systemd-run, I will have to look further into this. The umu variant shouldn't have this problem if you wish to try it.

@damccull what branch of nixpkgs are you on (ideally the commit as well)?

I am currently using nixos-unstable, and my flake.lock says.... (drumroll)
    "nixpkgs": {
      "locked": {
        "lastModified":<PHONE_NUMBER>,
        "narHash": "sha256-FUZpz9rg3gL8NVPKbqU8ei1VkPLsTIfAJ2fdAf5qjak=",
        "owner": "nixos",
        "repo": "nixpkgs",
        "rev": "c00d587b1a1afbf200b1d8f0b0e4ba9deb1c7f0e",
        "type": "github"
      },
      "original": {
        "owner": "nixos",
        "ref": "nixos-unstable",
        "repo": "nixpkgs",
        "type": "github"
      }
    },

This is what you wondered? I update every couple weeks but this is what I last tried it on and am currently running.

I cannot recreate your issue with this pr, I can on master.

Ok, I'll do a complete SC wipe and reinstall, including deleting the Wine folder, removing it from the config, running nix garbage collector. I'll also do an update of NixOS. Then I'll reinstall this PR and let you know what happens. I have no worries on bandwidth so I am happy to download the game again.

Shouldn't require reinstalling the game. Just ensure your flake input is targeting the update-star-citizen branch

I agree with you, but I did do that and nothing changed. So I'm going the nuclear route just to ensure there's nothing weird going on in my system. I've already begun, but it won't be a long process.

Well, this fixed it. Not sure what it was holding it back. Shortcut is working fine now. I wonder if it was just my shortcut that was jacked up. Either way, thank you for the effort in fixing this.

Would you mind telling me what was causing the problem so I can learn a bit more about wine and nix?

the launcher cant handle the logs outputting to the journal (which is what the desktop  shortcut does on gnome,  it uses systemd-run) this is just a work around for that by checking if the command is run from the terminal and if it isn't, route the output to a file.
Proton gets around this through other means: https://github.com/ValveSoftware/wine/commit/4703b100e324673214247b60a1172fae5f10c22e

How weird. I didn't think it would care where the logs go. Thanks for the link.

umu build failure is caused by https://github.com/Open-Wine-Components/umu-launcher/issues/296

pinging @fufexan for review


preface org as in print edition

Description
SICP: Preface years as in print edition

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 30.943%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3470

Relevant Lines:
10454

💛  - Coveralls


duplicate lib directories?

Some script/lib stuff showed up in lib: I was probably just copy-and-pasting carelessly.

Fixed in 0bec728


content_v2 API not being re-generated despite changes to discovery doc

Hi all,
There are recent changes in the content_v2 API (like new methods) that were released on 6/18 and have been reflected in the discovery doc. However, this API hasn't been regenerated since 6/12 and I'm unsure why. Please regenerate it as soon as possible, thanks! (If you know why it's not being regenerated, please let me know as well!)

My guess is the auto-generator won't replace older classes when it detects a conflict:
    conflict  google/apis/content_v2.rb
Overwrite /Users/googler/ruby/google-api-ruby-client/generated/google/apis/content_v2.rb? (enter "h" for help) [Ynaqdh] Y
       force  google/apis/content_v2.rb
    conflict  google/apis/content_v2/service.rb
Overwrite /Users/googler/ruby/google-api-ruby-client/generated/google/apis/content_v2/service.rb? (enter "h" for help) [Ynaqdh]
       force  google/apis/content_v2/service.rb
    conflict  google/apis/content_v2/classes.rb
Overwrite /Users/googler/ruby/google-api-ruby-client/generated/google/apis/content_v2/classes.rb? (enter "h" for help) [Ynaqdh]
       force  google/apis/content_v2/classes.rb
    conflict  google/apis/content_v2/representations.rb
Overwrite /Users/googler/ruby/google-api-ruby-client/generated/google/apis/content_v2/representations.rb? (enter "h" for help) [Ynaqdh]
       force  google/apis/content_v2/representations.rb

@dazuma there's an internal bug on this one as well

@mattwhisenhunt I merged #692. However, it looks like there's now some urgency on this one, to get a gem released within the next few days. Are you familiar with how the gem auto release works? Is it possible to trigger it manually?

Should be fixed in google-api-client version 0.23.2 (https://rubygems.org/gems/google-api-client/versions/0.23.2). This was apparently a symptom of a larger problem that we'll address in the toolchain (https://github.com/googleapis/discovery-artifact-manager/issues/86).


fixed a bug with invalid bytes in ASCII

Looks like ruby 1.9.3 is not supported by selenium any more.

This patch fixed the problem for me.

UTF-8 is not valid over the wire unless the mail server advertises 8-bit encoding, which MailCatcher does not. If you a receiving errors here then I'm afraid you or your mail library is not correctly encoding your sent email.

I'm using regular Rails 5 mailer. Of cause it's transfer encoding is  quoted-printable ascii. But inside it has one html part with utf8 encoding. What's wrong ?

SMTP is by default a 7-bit protocol:
https://tools.ietf.org/html/rfc821#page-3
So bodies containing bytes which require the high bit set must be encoded in some other form, usually quoted printable. The mail gem (used within rails) should probably be doing this for you transparently.
SMTP was only extended later to 8-bit by RFC5321 and then only when the server advertises a 8BITMIME capability which MailCatcher does not.

OK, fine. I said this above - rails 5 generates a letter with quoted printable ascii encoding. Over SMTP you receive quoted printable ascii encoding.
But after decoding it you will get plain-text and html parts with utf8 encoding.
And everything works fine, but String is marked as ASCII-8BIT and JSON crashes in a try to convert it to utf8.

The message["source"] is not decoded, it should be the literal SMTP transmitted message body which should be 7-bit ascii (which is valid utf-8). If you're getting an encoding error here then the message wasn't encoded properly and isn't a clean 7-bit subset of utf-8, so forcing it to be utf-8 by replacing bad characters is going to munge the source and lie about your message over json.

The only decoded part is that lines with double periods would be replaced with single periods.

The real solve here would be to make sure that the message source when received via SMTP contains only valid 7-bit bytes and raise the error earlier with clearer instructions on how to fix it in the sender.

(or just rewrite the whole smtp server and build in 8bit mime support supporting first-class encodings and again raising errors earlier in the smtp exchange when invalid content is supplied.)


Windows Widget implementation article is misleading - it makes you create a console app that shows a console window when showing widgets

For the main article documenting how to create a widget - it makes you waste time creating one that results in a console window showing in Windows Terminal whenever you show the widgets board. As I understand - widgets should be added to existing windowed or headless app and that part should definitely be included in the documentation.

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

ID: 1d81a1eb-10f9-caf2-7457-48df84ca543e
Version Independent ID: 1d81a1eb-10f9-caf2-7457-48df84ca543e
Content: Implement a widget provider in a win32 app (C++/WinRT) - Windows apps
Content Source: hub/apps/develop/widgets/implement-widget-provider-win32.md
Product: reunion
Technology: apps
GitHub Login: @drewbatgit
Microsoft Alias: drewbat

Thanks for the feedback. The how-to creates a console app to make debugging easier for people getting started with Windows widgets. But we have updated the guidance to include instructions for converting the resulting app from a console app to a Windows app so that the console doesn't show.


[release-0.29] chore: Update golang.org/x/* modules

What this PR does / why we need it:
Updated modules golang.org/x/* to the latest versions.
Special notes for your reviewer:
Release note:

None

Waiting for https://github.com/k8snetworkplumbingwg/ovs-cni/pull/288

/hold

/lgtm
/approve

Waiting for #288

merged

/hold cancel


[LENS-1939] Add custom json document support for Map and Collection type fields

This is a just a draft review for Barca Engineering Push source changes along with https://github.com/coveo/cosap-commerce-connector/pull/37.
I tried using separate JsonSerializers but it seems like Gson fails to use custom made serializers.

@jgwatkincoveo @samisayegh Just wanted to update on this change. Today I reverted this whole change and I can see that in the Content Browser both Dictionary and Collection fields are being set in a correct way (even tho we cannot see the whole price value but the default value is set correctly). In the metadata section of the source the price is still shown in a weird format (e.g. "{=[1200.0], bigfish=[960.0], smallfish=[1080.0]}"), and the related softwares (collection) field values are separated as single values (you can see that the sum of the percentages > 100%). In the snowflake the standard_fields column is empty.


Publish a Blazor Static Web App using an Azure DevOps pipeline

Hi,
I am hoping this is an easy fix.
I have followed the steps in the Deploy Blazor tutorial and all is well, my github action successfully deploys the repo to the website and I can click the Fetch data link and get results returned from the api.
https://docs.microsoft.com/en-gb/azure/static-web-apps/deploy-blazor
I have tried to replicate this using only Azure DevOps pipelines. I've imported the github repo into an Azure DevOps repo and then built a pipeline using the steps in this article:
https://docs.microsoft.com/en-gb/azure/static-web-apps/publish-devops
I then modified the build pipeline to include steps to build the blazor app and point at the correct locations:
trigger:

main

pool:
vmImage: ubuntu-latest
steps:

checkout: self
submodules: true
task: AzureStaticWebApp@0
inputs:
app_location: 'Client'
app_build_command: 'dotnet build'
output_location: 'wwwroot'
api_location: 'api'
api_build_command: 'dotnet build'
routes_location: '/Client/wwwroot'
env:
azure_static_web_apps_api_token: $(deployment_token)

This build "works" and the static website gets deployed and I can browse to it (so the Blazor app seems to work), but upon clicking the Fetch data link I can see a 404. It's as if the API just isn't there.
My question I hope is simple, is there some simple fix to the api_build_command for example?

The build runs on Linux and the file system is case sensitive. Can you change api_location: 'api' to api_location: 'Api'?
There should be no need to override the build commands for either api or app build as the task is capable of detecting and building Blazor WebAssembly and .NET Core 3.1 function apps, you can remove those lines.

Thanks @anthonychu I just noticed this and closed the issue, but good to know there's no need to add any custom build steps too.


Fixed typo

So, this in theory should fix the problem with firebase in issue #38 , right?

Yes, if the exception in the Gmail notifier occoured before the firebase
code and wasn't handled properly. Maybe the notification should always be
the last call.
niqdev<EMAIL_ADDRESS>schrieb am So., 18. Dez. 2016, 19:30:

Merged #41 https://github.com/niqdev/packtpub-crawler/pull/41.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/niqdev/packtpub-crawler/pull/41#event-897908991, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AEmPPETyyNASW88wfwGcZXowOLO58y_jks5rJXuugaJpZM4LP-xO
.

Well, at this point let's see if the script will still work next year :cold_sweat: