error

[14-12-2015 19:37] System.Runtime.Serialization.SerializationException: Expecting state 'Element'.. Encountered 'Text'  with name '', namespace ''.
at System.Runtime.Serialization.XmlObjectSerializerReadContext.HandleMemberNotFound(XmlReaderDelegator xmlReader, ExtensionDataObject extensionData, Int32 memberIndex)
at System.Runtime.Serialization.Json.XmlObjectSerializerReadContextComplexJson.GetJsonMemberIndex(XmlReaderDelegator xmlReader, XmlDictionaryString[] memberNames, Int32 memberIndex, ExtensionDataObject extensionData)
at ReadRootObjectFromJson(XmlReaderDelegator , XmlObjectSerializerReadContextComplexJson , XmlDictionaryString , XmlDictionaryString[] )
at System.Runtime.Serialization.Json.JsonClassDataContract.ReadJsonValueCore(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)
at System.Runtime.Serialization.Json.JsonDataContract.ReadJsonValue(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)
at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)
at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Type declaredType, DataContract dataContract, String name, String ns)
at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName)
at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
at System.Runtime.Serialization.Json.DataContractJsonSerializer.ReadObject(XmlDictionaryReader reader)
at POEApi.Model.POEModel.GetStash(Int32 index, String league, String accountName, Boolean forceRefresh)
[14-12-2015 19:37] JSON Serialization Failed: base64 bytes:
[14-12-2015 19:37] ZmFsc2U=
[14-12-2015 19:37] END
[14-12-2015 19:37] Error downloading stash for Standard, exception details: System.Exception: Downloading stash, details logged to DebugInfo.log, please open a ticket at https://github.com/Stickymaddness/Procurement/issues
at POEApi.Model.POEModel.logNullStash(Stream stream, String errorPrefix)
at POEApi.Model.POEModel.GetStash(Int32 index, String league, String accountName, Boolean forceRefresh)
at POEApi.Model.POEModel.GetStash(String league, String accountName)
[14-12-2015 19:37] System.Exception: Downloading stash for Standard, details logged to DebugInfo.log, please open a ticket at https://github.com/Stickymaddness/Procurement/issues
at POEApi.Model.POEModel.GetStash(String league, String accountName)
at Procurement.ViewModel.LoginWindowViewModel.LoadStashItems(Character character)
at Procurement.ViewModel.LoginWindowViewModel.d__6.MoveNext()
at System.Collections.Generic.List1..ctor(IEnumerable1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at Procurement.ViewModel.LoginWindowViewModel.<>c__DisplayClass2.b__1()
at System.Threading.Tasks.Task.Execute()

Are you logging in with sessionID? Have you checked that your account name is correct?

No im not using a session ID. Yes i have checked that my information is all correct.

Hey,
first of all, im using the session id, ive already optained an new id, deleted and redownloaded the acutal version, but that all doesnt helped.
i thougt a little about when the problem has shown up. at sunday i bought the accendency package, and upgraded my stash tabs from normal to premium. then i got the problems at the next procurement login on monday.
so may it be possible that there is a problem with the named premium stash tabs? or maybe the fact that i still have some old racing tabs with legacy items, that get downloaded before the actual season tabs?
just some thoughts, but i hope they help to track down the problem.

@Judaspriester Thanks for the info, premium tabs shouldn't be a problem as Procurement has supported them for a long time. I know of a few streamers that use Procurement that have hundreds of named tabs.
It's possible however that old race tabs are causing a problem. What you could try is setting Procurement to only download the talisman league your are playing in.
Beyond that, I have created a wiki article which covers this issue,
https://github.com/Stickymaddness/Procurement/wiki/Expecting-state-'Element'-error

Hey,
ive already seen ur wiki entry, but sadly it doesnt work for me. The deal with the racing tabs is, that they get still downloaded if i set it to only download talisman (even if they actually doesnt show up ingame). if i remember right they also show up before my common stash pages.
maybe i should realy think about cleaning them up.

Hey,
for ur information, i solved the problem for me by picking up an session id via internet explorer in stead of firefox.
i dont know why, but it works.

Procurement 1.9.8-RC1 has been released:
https://github.com/Stickymaddness/Procurement/releases/tag/1.9.8-RC1
Please retest with this version, if you are using sessionID first log out of the forum, clear your cookies and then log back in using the POESESSID cookie to get your sessionID.


add pagination

Description
We should be able to paginate the list of devices inside of a group. The parameter wasnt being passed in the route, so the default was 100.
Fixes # (issue)
Type of change
What is it?

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update
[ ] Refactor

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[X] I run go fmt ./... to check that my code is properly formatted
[X] I run go vet ./... to check that my code is free of common Go style mistakes

Test results are available in Ibutsu. The test run IDs are:
9014c113-b984-4b0d-8a86-87f3938d5140
ab8bf47d-7a1a-4b4a-bc9a-809d83119ae8

Test results are available in Ibutsu. The test run IDs are:
9fbe18cc-6275-4081-a3a8-8948b8ce1314
e2893378-4e5c-4dfa-8877-e44959428968


Logger in go

resolves https://github.com/open-traffic-generator/openapiart/issues/346

Covered by https://github.com/open-traffic-generator/openapiart/pull/422


how to keep users Logged-in in various integrations?

hello,
I am building a hubot which integrates with Github, Trello and Jenkins using users' access tokens.
Users must authenticate using oauth to receive an access token. The token i receive, i encrypt it and store it in a mongoDB.
When a user asks for something, hubot must call the specific API (i.e. https://api.github.com/user/repos) using user's token. So, hubot has to retrieve user's token from mongoDB, decrypt it and use it in the request. The above procedure (about retrieving the token) goes on every time a user asks something from that API..
So what i am asking is if there is a way to avoid this procedure every time a users asks for something. Is there any way to keep them logged in? Something like express-sessions for browsers. The problem with the express-sessions is that i have to use cookies which i guess is impossible or very difficult with hubot.
I was thinking about using redis brain. Is it good idea? how about the security?
thanks!
-Andreas
PS. i dont know where to ask so i asked here. i hope it's ok!

answered here from stack overflow


[BUG] meta description isn't truncated at 160 characters

Describe the bug
The meta description is not truncated after 160 characters. Microsoft Bing and other SEO-sensitive sites treats that as an error.
To reproduce
Steps to reproduce the behavior:

Create a post with more than 160 characters in text
generate the site
view source of genereated post and look for: meta name="description" content=
count the characters (e.g. use https://www.charactercountonline.com)

Expected behavior
Expected that the meta description is truncated at 160 characters
Log file
not applicable.
Screenshots

Environment (please complete the following information):

Hinode version: [e.g. v0.22.3]
Host OS:  macOS Sonoma 14.1.2
Node version: node v20.5.1
Hugo version: hugo v0.121.2-6d5b44305eaa9d0a157946492a6f319da38de154+extended darwin/arm64 BuildDate=2024-01-05T12:21:15Z VendorInfo=brew
Browser: Safari 17.1.2 (196<IP_ADDRESS>.12)

Additional context
I know it is better to have a handwritten description/summary, but since I don't have them for all articles, I would like to have it truncated.
The strange thing is that in layouts/partials/head/head.html description is truncated to 150 characters, but for some reason layouts/partials/head/seo.html doesn't use that truncated description.
As a workaround I edited seo.html and changed the line from
{{ $description := or (partial "utilities/GetDescription.html" .) .Site.Params.main.description  }}
to
{{ $description := or (partial "utilities/GetDescription.html" .) .Site.Params.main.description | truncate 160 }}
since 160 is the maximum advised. That way it will also be used for the

Thanks for spotting this! I released a fix in v0.22.4. I also improved the description itself. The revised version should no longer include HTML escape characters. See this commit for more details.


pure python version of uamqp

I am encountering several problems when cross-compiling this package because of the c file in it.
So I am wondering when will the pure python version be released?

hey @JackyXu866 , thanks for reaching out.
The goods news is that we've started planning and prioritizing to get the ball rolling again on pure python library.
However there is plenty of work on feature parity and test remaining to be done and we have limited cycles and resources allocated on uamqp library right now.
I'll make sure in the coming months time and efforts would be put on pure python implementation, but there's no guaranteed timeline.

And to help you out of the trouble, what kind of cross-compiling problems are you suffering from? I may know the solution or we could discuss.

hey @JackyXu866 , hope you're keeping well!
are you a user of the azure-eventhub SDK? If you're an azure-eventhub user, then we have good news for you :)
I'm excited to announce that we redesigned our Python EventHubs SDK to not rely on any C code anymore, it’s now entirely implemented in Python (5.8.0a3 - pypi). We’d love to get your feedback and perspective on this new version, as we believe you are using this SDK in an environment that would benefit from the changes.
Here are some highlights of the SDK :
•	Stability and robustness, eliminating any risks of C related memory leak or segmentation fault errors.
•	Full multi-platform support (ARM processors like M1, etc.)
•	Improved sending and receiving performance.
To get started, just install the wheel by command pip install azure-eventhub==5.8.0a3 in your Python environment and you're all set to go with your applications. This package is fully backward compatible, and no changes are needed in your application.
We’re eager to hear what you think. Please reply to this thread at any time with feedback or any questions you have for us! We’re all ears.

Thanks @simmel,
Indeed the intention is that the AMQP 1.0 implementation itself is going pure-python :)
While there will be a couple of Azure-specific features, the new library will follow the generic AMQP 1.0 specification.
However regarding the behaviour of the new library, one of our key considerations is backwards compatibility with our Azure SDKs (that is, compatibility with behaviour/errors/connection status/etc rather than API shape).
Therefore we've chosen to start the alpha of this library as a vendored package within our Azure EventHubs and ServiceBus SDKs while we get that early feedback before we publish it as a standalone package.
The pure-python version is being publicly developed is this branch:
https://github.com/Azure/azure-uamqp-python/tree/pyproto
So you are very welcome to install and try out from the repo until we reach a point where we are largely happy with the stability as the basis of our SDKs and can publish this to PyPI :)

Thank you @annatisch ! Dogfooding is always the best so it sounds like you're doing the right thing!
I'll try it out on some personal sideproject and let you know if I find something. Looks like the docs might not be up to date (at least the README) but the tests where up to date (and probably not even changed that much since you'll try to keep API compatibility) so I can start there.
Looking forward to having a Pure Python AMQP lib! That Microsoft would be the one to do it was not on my bingo card though ; )


Records counts aren't consistent

To reproduce:

Search for Orobanche and you should see 1 in the Records column for Orobanche hederae
Click on Orobanche hederae
3020 records are apparently returned, filling the whole map with dots - there should be only 1 dot and 1 site.

Even if there is supposed to be 3020 records in the results, only those on the current page should be shown. It looks like all records from all pages are being show at the moment.

Which branch are you on, Charles?
This is my local develop branch, works ok for me.
@.***D7352D.9948E250]
From: Charles Roper @.>
Sent: 18 April 2021 04:05
To: jdrever/ShropBotSoc @.>
Cc: James Drever @.>; Assign @.>
Subject: [jdrever/ShropBotSoc] Records counts aren't consistent (#102)
To reproduce:

Search for Orobanche and you should see 1 in the Records column for Orobanche hederae
Click on Orobanche hederae
3020 records are apparently returned, filling the whole map with dots - there should be only 1 dot and 1 site.

Even if there is supposed to be 3020 records in the results, only those on the current page should be shown. It looks like all records from all pages are being show at the moment.
https://user-images.githubusercontent.com/176/115132774-07b76800-9ffb-11eb-8347-40035f5e8191.png
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://github.com/jdrever/ShropBotSoc/issues/102, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAPKYJPBUGETYKIAQGJTD33TJJD6LANCNFSM43DXLGNQ.

This was on branch 4.2.2-map-showing...
See PR #100
I probably broke something making changes there.

Looks like the difference is that double quotes aren’t surrounding the taxon_name in the API call..  Can’t quite see why that would be the case looking at differences in the code.  And the API is being so flakey at the moment, I think I need to take a break 😊
From: Charles Roper @.>
Sent: 19 April 2021 15:33
To: jdrever/ShropBotSoc @.>
Cc: James Drever @.>; Assign @.>
Subject: Re: [jdrever/ShropBotSoc] Records counts aren't consistent (#102)
This was on branch 4.2.2-map-showing...
See PR #100https://github.com/jdrever/ShropBotSoc/pull/100
I probably broke something making changes there.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://github.com/jdrever/ShropBotSoc/issues/102#issuecomment-822514068, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAPKYJP35ZHZDCED7VHKDHTTJQ5I7ANCNFSM43DXLGNQ.

Closed, after spotting that stripping quotes out in NBNRecords was causing the issue.


⚠ GitLab Server has degraded performance

In 034f94d, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 3101 ms

Resolved: GitLab Server performance has improved in ce7ae0d.


Support prefix for executor

Add support for using prefixes see (http://docs.pyinvoke.org/en/1.3/api/context.html) when using j.core.executorsl

@alichaddad why this is needed? is it for builders?

I think it will be generally good to have, can't recall the context exactly.


Analyzer does not throw a compile error when type in the right part of typedef is not well-bounded

Dart SDK Version: 2.3.0-dev.0.5
OS: Windows 10 64 bit
The following source example declares a typedef AAlias with Function in the right part:
class A<X extends A<X>> {}
typedef AAlias = Function<X extends A<X>> ();
main() { print("OK"); }

Dart throws a compile time error here whereas analyzer passes without any errors or warnings. Sample output is:

$> dartanalyzer test.dart
$> dart test.dart
test.dart:2:39: Error: Type 'X' not found.
typedef AAlias = Function<X extends A> ();
$>

Seems like analyzer should throw an error here too.

This is actually an issue with the front end (and the error is still reported with dart from 762113758de67ea48310f87161f4f31b33fd9551):
It is not an error to use X in the bound A<X>, because any generic function type (including one that occurs on the right hand side of a typedef) should have a scope where its type parameters are introduced, such that the type parameters can be used in F-bounds.
Changed the labels and issue title to reflect this.

Just checked, the issue arises independently of the type alias:
class A<X extends A<X>> {}
Function<X extends A<X>>() f = throw 1; // Error in CFE: Type `X` not found.
main() {}

So, apparently, function types never introduce the scope where X can be found when checking a bound like A<X>, or it does get created but it isn't made the current scope of the bounds.


add profile for Livarno Lux (Lidl) HG08131A

Device information
This device is the currently sold GU10 bulb generation by Lidl under the Livarno Lux branding:
https://www.lidl.de/p/livarno-home-leuchtmittel-rgb-zigbee-smart-home/p100348095001
5 W
CT: 2000 - 6500 K + RGB
Home Assistant Device information

Livarno Lux GU10 spot RGB (HG07834A/HG09155A)
by Lidl

(This listing is currently missing the HG08131A, issue ticket for this for z2m can be found here: https://github.com/Koenkk/zigbee2mqtt/issues/24591)
Checklist

[x] I have created a single PR per device. When you have multiple submissions please create separate PR's.
[x] For lights - I have only included the gzipped files (*.gz), not the raw CSV files.
[x] For lights - I have provided a CSV file per supported color mode. Look that up in Developer Tools -> States

Additional info

@bramstroker the bot creating the images failed on the first attempt :)

Thanks!

@RubenKelevra I noticed json schema validation for models was not working correctly anymore.
I have fixed that locally, but when running I noticed this profiles fails validation.
One of the checks is that the standby power should not be impossible low.
In this case it's 0.03, which we never saw on any of the lights in the library.
These devices with Zigbee radio typically consume 0.2-0.3W.
Could you try measuring only standby power again by turning the light of manually and see what power reading you get?

Yeah I think this was caused by drifting: I didn't preheated the resistors prior to measuring them with measure script and thus their consumption dropped over the span of the test, which leads to too low readings at the end of the measurement.
That's why I've added this note to the measure script the other day.
The measurement itself looks quite noisy, too. So I think it makes sense that I setup multiple of these lights and redo the whole measurement, as the upper end of the measurement is screwed by the drift as well.

@bramstroker maybe it makes sense to do the standby measurement twice: One time in the beginning one time at the end and compare both. Of they within 0.1 W we let that pass and use the average, but otherwise we print a warning that the measurement is inconsistent and export it just as 0 to the json.
This would help that we can discuss with the contributor better ways to measure it.


even if running with manager enabled, automatically save reports into files, such that can be loaded later if needed

after #117 is implemented, this is easy

now we already have a switch as well as compile time flag. so users can choose easily.


Query 20150129_032824_00012_rhk3t, STARTING, 0 nodes, 0 splits, Why?

I have made a presto cluster wtih 25 nodes(machines). I found a very strange issue.
when I run a Query like:  select count(1) as pv, inter_name from hive_yz.acorn_3g.mcs_access where log_date = '2015-01-27' group by inter_name order by pv desc limit 10;
First time, 10 querys run at the same time and only 2 querys got rigth answer, 2 querys got crashed, 6 querys got the right answer but made my terminator no response。
So I know, because the resources are not enough to meet the 10 querys running at the same time.
Then, I decided to try 5 querys at the same time, but this time I got the strange message like this:
Query 20150129_032824_00012_rhk3t, STARTING, 0 nodes, 0 splits
Query 20150129_032824_00012_rhk3t failed: java.lang.Exception: java.util.concurrent.TimeoutException: Timeout waiting for task.
And now, there is no query can work. So I guess there is something makes my cluster out of work. I don't know  why and how to solve it.

 Please re-open, if this is still an issue


In-Memory SQLite DB

Hi,
In the documentation for SQLiteOpenHelper it mentions that you can send null as the value for name parameter in its constructor to create an in-memory DB. It seems like the design of FlowSQLiteOpenHelper prevents one from doing this. Is there another way to accomplish this in DBFlow? If not, could one accomplish this by forking the project and simply adding a constructor to FlowSQLiteOpenHelper, or does the general design of DBFlow preclude this sort of thing? Thanks!
John

@johntvolk its meant not to be in memory, rather on disk since all code is precompiled and analyzed pre-runtime. Never even knew you could create an in-memory DB. If you forked the project, would it work?

@agrosner We haven't ended up needing this yet, but we may take a look in the next few months again. Would you be interested in looking at a PR for this if we figured it out?

fixed in 3.0.0+


Ensure the viewer properly supports 2d models (i.e. DrawingViewDefinition)

If needed/prioritized, we can reopen.


Points to revert commit in cdbjs

@CartoDB/frontend

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)


std_fit(v) should be universally the same as std_reserve(v, std_size(v))

Remove implements_fit and stdlib_vector_fit() implementation etc

Done.


Currently I cannot connect to my service links

It is not possible for me to connect to the service link at the moment.
I have got a set up with 3 Rancher hosts they are all alike, however 1 get is online 24/7 and 2 spawns in the morning and shut down in the evening. A few days back around when I upgraded to 0.56.1 I experienced issues with spawning Jenkins agents on my 2 daily spawned hosts. These try to connect to master:8080 and master refers to Jenkins master instance. This however doesn't work. When I log onto the 24/7 host it works just fine, but the two other hosts have no connectivity, although they can resolve the host master to an ip.
These servers are hosted in AWS and have the same settings and bootup sequence.
I am running
Rancher 0.56.1
Rancher Agent 0.82.0
/Marcus

I have two issues apparently, one being Jenkins API doesn't work so I cannot create a JNLP entry (off topic), however if I re-point my access to the ip of the Jenkins Master instead of the Service Link host name it works fine.
http://master:8080/ (internal docker service link) -> http://jenkins.company.com/ (internally available)
I am unable to ping master as well as wget/curl the url, it just can't connect.

When your hosts spawn in the morning, have you confirmed their cross host communication is working? Can you exec into the network agent on the 24/7 host and try to ping the Rancher managed IP of the network agent (i.e. ping 10.42.x.x) on one of the newly spawned hosts?

@MarcusSjolin Please re-open if you are able to provide more details on your setup based on the questions I had asked.


darwin: Make context creation more flexible

On OS X the opengl major/minor version is really only a lose suggestion because you'll always get the highest core context available no matter what gl version you request. This is in line with how most (if not all) window libraries are handling it.
https://github.com/glfw/glfw/blob/fa602692455d87e11c9ff5a5fb0681ca6403772a/src/nsgl_context.m#L234-L246

I can make PR for 1.4 as well. Just waiting for judgement!

Looks good to me.


Issue with post frontmatter and pagination

I have some problems when using post's frontmatter and paginating. Additional properties I define in the a post's frontmatter are not available when I use pagination.
E.g. I have this post:
---
layout: default
title: 'Some post'
customfield: 'bar'
---
## Hello World!

And my index.html look like this
---
layout: default
paginate: 1
title: 'A different title'
---
{% for post in paginator.posts %}
  {{ post.title }}-{{ post.customfield }}
{% endfor %}

Then the first page is rendered with
  Some post-

but I expect
  Some post-bar

I'm always confused by Pretzel's code: on the one hand PageContext has several properties, and on the other hand it has a Bag, where some of the properties are duplicated.
This PR contains "only" a unit test to reproduce the issue. I don't know how to fix it at the moment.

Thanks a lot for the reporting 😃
I know that the paginator is kind of "weird" at best, but I hadn't take the time to investigate it.
Seems the time has come!

So finally it is not linked to the paginatordirectly but by the way we populate the liquid's template data in LiquidEngine: the paginator is passed directly without processing the data of each of his posts.
So right now the customfield is accessible through post.bag["customfield"].
An evolution could be to pass the paginator in LiquidEngine.CreatePageData but to call a ToHash method, like the one used on ContextDrop, which will return a Hash of all properties of paginator and call ToHash on each Page.
About PageContext, I think it is because Razor is also supported: it doesn't use page.customfield but @Model.Bag["customfield"] to access to custom values in page. So the properties are needed to facilitate the access to usual values.


xxd -i: not expected behaviour

As far as I can tell the upstream for the default xxd is vim, with an example of the expected xxd -i behavior from there ( https://vim.fandom.com/wiki/Hex_dump#Generating_C_source_for_a_binary_file )
xxd -i in toybox just gives the bytes converted to hex with ,  in between without the required c.
In the example provided toybox xxd -i would give
  0x00, 0x01, 0x02, 0x03, 0x30, 0x31, 0x32, 0x33, 0x04, 0x05, 0x06, 0x07,
  0x44, 0x45, 0x46, 0x47, 0x10, 0x11, 0x12, 0x13, 0x14, 0x15, 0x16, 0x17,
  0x18, 0x19, 0x1a, 0x1b, 0x1c, 0x1d, 0x1e, 0x1f

and not the expected:
unsigned char sample_bin[] = {
  0x00, 0x01, 0x02, 0x03, 0x30, 0x31, 0x32, 0x33, 0x04, 0x05, 0x06, 0x07,
  0x44, 0x45, 0x46, 0x47, 0x10, 0x11, 0x12, 0x13, 0x14, 0x15, 0x16, 0x17,
  0x18, 0x19, 0x1a, 0x1b, 0x1c, 0x1d, 0x1e, 0x1f
};
unsigned int sample_bin_len = 32;

that one's my fault... i did this deliberately because i thought the vim
xxd behavior was too C-centric and i wanted to be able to use it for other
languages. but i should probably have just matched the vim xxd and made a
start on hexdump (which is what most people seem to use to solve this
particular "binary to hex array" problem, if the Android codebase is
anything to go by).
i'll send a patch tomorrow if rob doesn't say he's already done it...
On Wed, Jun 23, 2021 at 5:11 AM aheirman @.***> wrote:

As far as I can tell the upstream for the default xxd is vim, with an
example of the expected xxd -i behavior from there (
https://vim.fandom.com/wiki/Hex_dump#Generating_C_source_for_a_binary_file
)
xxd -i in toybox just gives the bytes converted to hex with , in between
without the required c.
In the example provided toybox xxd -i would give
0x00, 0x01, 0x02, 0x03, 0x30, 0x31, 0x32, 0x33, 0x04, 0x05, 0x06, 0x07,
0x44, 0x45, 0x46, 0x47, 0x10, 0x11, 0x12, 0x13, 0x14, 0x15, 0x16, 0x17,
0x18, 0x19, 0x1a, 0x1b, 0x1c, 0x1d, 0x1e, 0x1f
and not the expected:
unsigned char sample_bin[] = {
0x00, 0x01, 0x02, 0x03, 0x30, 0x31, 0x32, 0x33, 0x04, 0x05, 0x06, 0x07,
0x44, 0x45, 0x46, 0x47, 0x10, 0x11, 0x12, 0x13, 0x14, 0x15, 0x16, 0x17,
0x18, 0x19, 0x1a, 0x1b, 0x1c, 0x1d, 0x1e, 0x1f
};
unsigned int sample_bin_len = 32;
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/landley/toybox/issues/286, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMVLEWAZST3KFVFS53AMOBLTUHFPBANCNFSM47FVJRLA
.

On 6/23/21 7:08 PM, enh-google wrote:

that one's my fault... i did this deliberately because i thought the vim
xxd behavior was too C-centric and i wanted to be able to use it for other
languages. but i should probably have just matched the vim xxd and made a
start on hexdump (which is what most people seem to use to solve this
particular "binary to hex array" problem, if the Android codebase is
anything to go by).
i'll send a patch tomorrow if rob doesn't say he's already done it...

Have -C produce the prefix/suffix and -i by itself do the current behavior?
It will make Denys sad, but isn't less conformant than what we have now (and
thus not a regression).
Rob

Have -C produce the prefix/suffix

Do you mean xxd -C or xxd -C -i because xxd -C -i would be 'more' compliant.
Although I would prefer xxd -i to behave as expected, since I've used it in build scripts and I'm not alone(https://github.com/caramelli/yagears, don't want to look for more examples).
I don't know if many people/projects use xxd -i in the toybox way.

annoyingly, the default vim xxd output isn't ideal for C either --- the use
of int rather than size_t causes warnings, and there's no easy way to mark
both variables static or const or visibility hidden or...
looking at the callers in Android that seem to rely on the current
behavior, it doesn't look like many (4?), and since it's clearly my fault
i'm happy to own cleaning up the mess.
how does making xxd -i behave like vim xxd, but adding a flag something
like --bare to not include any boilerplate? (since although we could add
flags for golang or whatever alongside one for C, like i said: there's no
One True Answer for C anyway, so i'd assume other languages have equivalent
problems too. and even if they don't have those problems, anecdotally i'd
say most callers don't like the way vim xxd chooses a name for the
variables, and sed their own in after the fact anyway![1])
if we do go this way, i'll probably try to get in a no-op --bare before i
change -i, because that'll make the transition easier for me. only two of
them seem to be used as part of the build anyway --- people seem to be
writing scripts but checking in the [hand-modified] output :-(

https://codesearch.debian.net/search?q=xxd.*-i&literal=0&page=1 suggests
that most/all vim xxd users are post-processing the output too.[2]
the same search also shows that almost no-one is using the -include
longopt.

On Thu, Jun 24, 2021 at 7:17 AM aheirman @.***> wrote:

Have -C produce the prefix/suffix
Do you mean xxd -C or xxd -C -i because xxd -C -i would be 'more'
compliant.
Although I would prefer xxd -i to behave as expected, since I've used it
in build scripts and I'm not alone(https://github.com/caramelli/yagears,
don't want to look for more examples).
I don't know if many people/projects use xxd -i in the toybox way.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/landley/toybox/issues/286#issuecomment-867674147, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AMVLEWHGJA4QWFL6VICAYDTTUM47VANCNFSM47FVJRLA
.

On 6/24/21 9:17 AM, aheirman wrote:

Have -C produce the prefix/suffix

Do you mean |xxd -C| or |xxd -C -i| because |xxd -C -i| would be 'more' compliant.

I'd meant -C would override -i if both were provided, but I'm not a user of this
tool...

Although I would prefer |xxd -i| to behave as expected, since I've used it in
build scripts and I'm not alone(https://github.com/caramelli/yagears
https://github.com/caramelli/yagears, don't want to look for more examples).
I don't know if many people/projects use |xxd -i| in the toybox way.

That's a queston for Elliott, for builds internally within android.
Another option is to make -i behave conventionally and -I do the unwrapped
version, but I dunno what (if any) android build scripts would need to be
adjusted for this? Hmmm...
system/bt/gd/dumpsys/internal/test_data/mkfiles:xxd -i string.bfbs > string_bfbs.h
system/bt/gd/dumpsys/internal/test_data/mkfiles:xxd -i integer.bfbs > integer_bfbs.h
system/bt/gd/dumpsys/internal/test_data/mkfiles:xxd -i float.bfbs > float_bfbs.h
system/bt/gd/dumpsys/internal/test_data/mkfiles:xxd -i struct.bfbs > struct_bfbs.h
device/generic/vulkan-cereal/third-party/angle/src/libANGLE/renderer/metal/shaders/gen_mtl_internal_shaders.py:
os.system('xxd -i compiled/default.ios_sim.metallib >>
compiled/mtl_default_shaders.inc')
rs/gen_mtl_internal_shaders.py:    os.system('xxd -i
compiled/default.ios.metallib >> compiled/mtl_default_shaders.inc')
looks like grep -r is finding quite a few. (Denys Vlasenko's recent admonition
comes to mind...)
Rob

On Thu, Jun 24, 2021 at 9:56 AM Rob Landley @.***>
wrote:

On 6/24/21 9:17 AM, aheirman wrote:

Have -C produce the prefix/suffix
Do you mean |xxd -C| or |xxd -C -i| because |xxd -C -i| would be 'more'
compliant.

I'd meant -C would override -i if both were provided, but I'm not a user
of this
tool...

Although I would prefer |xxd -i| to behave as expected, since I've used
it in
build scripts and I'm not alone(https://github.com/caramelli/yagears
https://github.com/caramelli/yagears, don't want to look for more
examples).
I don't know if many people/projects use |xxd -i| in the toybox way.

That's a queston for Elliott, for builds internally within android.
Another option is to make -i behave conventionally and -I do the unwrapped
version, but I dunno what (if any) android build scripts would need to be
adjusted for this? Hmmm...
system/bt/gd/dumpsys/internal/test_data/mkfiles:xxd -i string.bfbs >
string_bfbs.h
system/bt/gd/dumpsys/internal/test_data/mkfiles:xxd -i integer.bfbs >
integer_bfbs.h
system/bt/gd/dumpsys/internal/test_data/mkfiles:xxd -i float.bfbs >
float_bfbs.h
system/bt/gd/dumpsys/internal/test_data/mkfiles:xxd -i struct.bfbs >
struct_bfbs.h

yeah, but if you look at those files, it's one of the examples i mentioned
where they've run this once manually and checked in the results (and were
clearly using the vim xxd). so this particular example would be "fixed" by
making toybox xxd -i output the boilerplate.

device/generic/vulkan-cereal/third-party/angle/src/libANGLE/renderer/metal/shaders/gen_mtl_internal_shaders.py:
os.system('xxd -i compiled/default.ios_sim.metallib >>
compiled/mtl_default_shaders.inc')

likewise. the constexpr on the line above is to mark the array const (but
there's nothing they could [easily] do about the size). but, again, they
just ran this once and checked in the output.

looks like grep -r is finding quite a few. (Denys Vlasenko's recent
admonition
comes to mind...)

yeah. i think i made this mistake in xxd before i started switching the
Android build over. didn't really plan ahead there.
but like i said (a) i made this mess so it's only fair if i have to clean
it up [though obviously i can't clean up non Android stuff, but
presumably there isn't much of that?] and (b) afaict there are only
actually 3-4 places where the toybox xxd is actually in "live" use anyway,
if you ignore places like those above where someone ran a script manually
and checked in the (sometimes hand-edited!) result.

Rob
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/landley/toybox/issues/286#issuecomment-867800663, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AMVLEWE5UTLHWX74QKHFMT3TUNPSLANCNFSM47FVJRLA
.

cc-ing the toybox mailing list on this reply. And I also pinged
http://lists.busybox.net/pipermail/busybox/2021-June/088931.html because it's
just too on the nose not too. (When you're right, you're right...)
On 6/24/21 11:21 AM, enh-google wrote:

annoyingly, the default vim xxd output isn't ideal for C either --- the use
of int rather than size_t causes warnings, and there's no easy way to mark
both variables static or const or visibility hidden or...

The existence of xxd -C and -u to micromanage the -i output seems kind of
awkward as well. (And xxd -E is just inexcusable.)
What you've implemented is compatible with python and java and so on. Heck,
probably fortran. CSV is a lingua franca. Heck, bash can grok it:
$ toybox xxd -i README | while read -d, i; do printf \${i:1}; done
It's definitely the way they SHOULD have done it in the first place, but
unfortunately they didn't. The problem is compatibility with existing tools that
do extra stupid stuff by default...

looking at the callers in Android that seem to rely on the current
behavior, it doesn't look like many (4?), and since it's clearly my fault
i'm happy to own cleaning up the mess.

Yay cleaning.
I lean towards adding a capital version of the existing option (-I) that skips
the header/trailer stuff, and we can even poke the vim guys about it to make
Denys happy. :)
The "compatible" alternative is to add --gratuitous-longopt-with-no-short which
is less of a contested namespace. Of course it still breaks EXACTLY the same way
if you run AOSP with the vim tool instead of the toybox one, and by that logic
nobody would ever add another short option again.

how does making xxd -i behave like vim xxd, but adding a flag something
like --bare to not include any boilerplate? (since although we could add
flags for golang or whatever alongside one for C,

Oh please no. It's trivial to wrap the xxd output with header/footer lines, and
that's the "unix" way of doing things. Simple tools that connect together with
pipelines. As much of a fan of lua as I am, I'm not adding explicit support for
it to xxd.
The c output is grandfathered in, hysterical raisins etc. We can poke vim (and
again, busybox) to add the new "bare" output type.

like i said: there's no
One True Answer for C anyway,

It wasn't xxd's job to get C output syntax right in the first place, trying to
get it right for MORE languages is not going to decrease the entropic attack
surface.

so i'd assume other languages have equivalent
problems too. and even if they don't have those problems, anecdotally i'd
say most callers don't like the way vim xxd chooses a name for the
variables, and sed their own in after the fact anyway![1])

Indeed. I vote for "xxd -I" doing the unwrapped version but also recuse myself
from actual decision making here because I'm not a regular user of this tool and
Elliott is (and he has an existing userbase of scripts to migrate, the only
regression tests I have are artificial ones in tests/xxd.test which prove
nothing in this sort of circumstance).

if we do go this way, i'll probably try to get in a no-op --bare before i
change -i, because that'll make the transition easier for me.

How about we add -I as a synonym for -i and then switch toybox over to have -i
produce the conventional C output in a couple weeks?
I expect Denys is going to make us contact vim before busybox about the new
option this time, but I'm personally ok with that because vim isn't a gnu
project nor is it GPLv3. (Heck, its developer says on his web page he can be
outright bought: https://www.vim.org/sponsor/index.php .)
Although I expect "sending him a patch" is likely to work. :)

only two of
them seem to be used as part of the build anyway --- people seem to be
writing scripts but checking in the [hand-modified] output :-(

Do I have a https://landley.net/toybox/cleanup.html#advice link about not
checking in generated files? No? I'm sure I've ranted about it before. Possibly
in my blog.
I was in favor of it as the lesser evil when the linux kernel used it to avoid
having kconfig depend on lex, and toybox has kconfig/*_shipped files inherited
from that. But that's ALSO another reason to reimplement the kconfig directory
from scratch.
Rob

On 6/24/21 12:50 PM, Rob Landley wrote:

I lean towards adding a capital version of the existing option (-I) that skips
the header/trailer stuff, and we can even poke the vim guys about it to make
Denys happy. :)

boggle
I started to patch the vim one and... it already supports this? It won't produce
header/footer output for stdin:
$ echo "look ma no header/footer" | xxd -i
0x6c, 0x6f, 0x6f, 0x6b, 0x20, 0x6d, 0x61, 0x20, 0x6e, 0x6f, 0x20, 0x68,
0x65, 0x61, 0x64, 0x65, 0x72, 0x2f, 0x66, 0x6f, 0x6f, 0x74, 0x65, 0x72,
0x0a
And both the busybox and toybox ones already get this right?
We can still add -I if you like, but... seems less vital now?
Rob


Update API and add support for small molecules

This PR makes some pretty large API changes, but provide a lot more flexibility than before.
Changed

PeptideTransformer* is now AnalyteTransformer* to reflect support for small molecules as well.
Similarly, PeptideDataset was renamed AnalyteDataset.
All the forward() methods for the Transformer modules have been updated to with additional keyword arguments. This enables BERT-style masking for training and such.
All transformer modules now have a global_token_hook() method. This can be overwritten in a subclass to customize how a global token (the first element of the sequence) is created using the *args and **kwargs provided in the forward methods.

Added

A new tokenizer for small molecules, MoleculeTokenizer.
The PeptideIonTokenizer.calculate_precursor_ions() method is fully PyTorch, so it should be efficient for use during model training and inference. (see https://github.com/Noble-Lab/casanovo/pull/269)

Next PR will be docs!

Thanks a lot @bittremieux! It turns out a missed a lot of documentation and you caught at least two potential bugs 🎉
Sorry the update has so many new changes - Ruff updated and apparently added another rule to the autoformatting.

I'm going to go ahead and merge so I can build atop this. @bittremieux, if there's anything else please let me know and I'll address it in a fresh PR!


Experimenting with weaver generate templates.

This PR experiments with weaver generate using templates to generate code. If we think it's more readable, I can covert the whole generator. Otherwise, I'll abandon the change.

Thanks for the explanation Sanjay! I played around with converting generateEncDecMethods to use templates, and I think it makes the code worse, so I'll abandon this change.
Another metric I looked at, besides the fraction of literal text to template size, is the amount of repetition in the template. The code  I templatized in the PR has a lot of repetition—the component name is used again and again—which makes the template more useful. Most of other generated code has less repetition, making the templates less useful.

I wonder if we can clean up the generated code a bit by using a generic
codegen.Register function.
On Fri, Apr 21, 2023 at 9:50 AM Michael Whittaker @.***>
wrote:

Thanks for the explanation Sanjay! I played around with converting
generateEncDecMethods to use templates, and I think it makes the code
worse, so I'll abandon this change.
Another metric I looked at, besides the fraction of literal text to
template size, is the amount of repetition in the template. The code I
templatized in the PR has a lot of repetition—the component name is used
again and again—which makes the template more useful. Most of other
generated code has less repetition, making the templates less useful.
—
Reply to this email directly, view it on GitHub
https://github.com/ServiceWeaver/weaver/pull/278#issuecomment-1518093802,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB5YZUMKC36NJC3DRJQQBJDXCK3GLANCNFSM6AAAAAAXF7JV3I
.
You are receiving this because you were mentioned.Message ID:
@.***>

Oh, interesting idea. Let me look into that.


Add instructions for cleaning up after CMake build

Hi! Would be curious to hear about the issues that you've had with building a second time.   It shouldn't be necessary to nuke the build folder

Just tested in the docker image (https://github.com/OpenSpace/docker/blob/master/build/ubuntu-2204-gcc13.Dockerfile) and it works for me to build twice:

git clone --recursive --jobs 8 --depth 1 https://github.com/OpenSpace/OpenSpace
cd OpenSpace
mkdir build
cmake -S . -B ./build
cmake --build build --parallel 24
...
cmake --build build --parallel 24 again

root@b384e20c7345:/OpenSpace# cmake --build build --parallel 24
[  0%] Built target websocketpp-configure
[  0%] Built target TracyClient
[  0%] Built target lz4
[  0%] Built target simdutf
[  0%] Built target stb_image
[  1%] Built target zlibstatic
[  1%] Built target codegen-lib
[  1%] Built target tiny-process-library
[  2%] Built target Lua
[  2%] Built target ryu
[  2%] Built target Imgui
[  3%] Built target freetype
[  3%] Built target tinyxml2
[  4%] Built target soloud
[  4%] Built target glad
[  6%] Built target cfitsio
[  6%] Built target nlohmann_json_schema_validator
[  6%] Built target zlib1
[  6%] Built target websocketpp-build
[  6%] Built target codegen
[  8%] Built target glbinding
[ 11%] Built target libcef_dll_wrapper
[ 12%] Built target glfw
[ 12%] Generating __codegen_unittest.h
codegen /OpenSpace/support/coding/codegen/tests/execution_enums /OpenSpace/support/coding/codegen/tests/execution_luawrapper /OpenSpace/support/coding/codegen/tests/execution_misc /OpenSpace/support/coding/codegen/tests/execution_structs
[ 12%] Built target scn
[ 13%] Built target minizip
[ 13%] Generating __codegen.h
codegen modules src
[ 14%] Built target png
[ 14%] Built target CCfits
[ 14%] Built target websocketpp
0/0 files changed in 13.696444 ms.  Pure time in codegen: 0 ms
[ 14%] Built target run_test_codegen
[ 14%] Built target OpenSpace_Helper
[ 14%] Built target glbinding-aux
[ 16%] Built target Catch2
[ 16%] Built target Catch2WithMain
0/322 files changed in 28.659409 ms.  Pure time in codegen: 0 ms
[ 16%] Built target run_codegen
[ 17%] Built target sgct
[ 22%] Built target assimp
[ 22%] Built target SGCTTest
[ 25%] Built target Ghoul
[ 25%] Built target GhoulTest
[ 75%] Built target spice
[ 78%] Built target openspace-core
[ 78%] Built target openspace-module-fitsfilereader
[ 78%] Built target openspace-module-audio
[ 78%] Built target openspace-module-debugging
[ 78%] Built target openspace-module-atmosphere
[ 78%] Built target openspace-module-digitaluniverse
[ 79%] Built target openspace-module-webbrowser
[ 79%] Built target openspace-module-webgui
[ 80%] Built target openspace-module-statemachine
[ 80%] Built target openspace-module-sync
[ 80%] Built target openspace-module-galaxy
[ 80%] Built target openspace-module-vislab
[ 81%] Built target openspace-module-imgui
[ 81%] Built target openspace-module-spacecraftinstruments
[ 81%] Built target openspace-module-toyvolume
[ 83%] Built target openspace-module-base
[ 83%] Built target openspace-module-cefwebgui
[ 83%] Built target openspace-module-volume
[ 83%] Built target openspace-module-gaia
[ 84%] Built target openspace-module-skybrowser
[ 84%] Built target openspace-module-space
[ 92%] Built target geos
[ 92%] Built target geos_c
[ 92%] Built target openspace-module-exoplanets
[ 92%] Built target openspace-module-server
[ 93%] Built target openspace-module-globebrowsing
[ 93%] Built target openspace-module-video
[ 94%] Built target openspace-ui-launcher
[ 94%] Built target OpenSpace
[ 98%] Built target codegentest
[100%] Built target OpenSpaceTest
root@b384e20c7345:/OpenSpace#

@alexanderbock thanks for your attention on this and pointing me toward the docker repo. I believe the initial error I was seeing about CMake files needing to be removed was a result of the source having changed. For context, I built from source a month or two ago following instructions here. I'm now attempting to build again after pulling in upstream changes. Initially I received errors suggesting to remove the CMake files as indicated in this PR, but then I found I was still unable to successfully build. I've since succesfully completed a build with the docker image you linked to, but I'm unable to with this ubuntu default one (which more accurately represents my system). So there may be two build issues I've encountered:

Running successive builds after source changes may require cleaning
The Ubuntu default build does not appear to be succeeding

It seems that gcc 11 and 12 both err while gcc 13 seems ok. Suspicious commit
OpenSpace/support/coding/codegen/lib/snippets.cpp:28:10: fatal error: format: No such file or directory
   28 | #include <format>
      |          ^~~~~~~~
compilation terminated.
make[2]: *** [support/coding/codegen/lib/CMakeFiles/codegen-lib.dir/build.make:104: support/coding/codegen/lib/CMakeFiles/codegen-lib.dir/snippets.cpp.o] Error 1

Ah.. Yea, as of about 2 weeks ago, we upped our compile requirements, but I haven't had time to change the docs page accordingly.  Since Ubuntu 24.04 is expected to ship with GCC13, we updated it to: MSVC 19.39, GCC 13, and Clang 17 as a minimum

@alexanderbock I've repurposed this PR for instructions on how to install gcc-13 on Ubuntu 22.04.


⚠ Bofrost.nl has degraded performance

In dccd969, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 1388 ms

Resolved: Bofrost.nl performance has improved in 47c6d44.


refactor: vscode-emmet-helper has been renamed to @vscode/emmet-helper

fix #163

@microsoft-github-policy-service agree [company="{your company}"]

@microsoft-github-policy-service agree [company="{your company}"]

@microsoft-github-policy-service agree

Thanks for the PR @nnmax. Unfortunately I am currently deprecating this project in favor of its more well maintained fork: https://github.com/styled-components/typescript-styled-plugin
So no big changes will be going into this repo
Can you please resubmit this PR against them? The change should be the same


Implement drag and drop

Support dragging scenes into the scene editor to spawn them.

Yeah, that is something I wanted to do, but really don't know how I'd do.

It works really well! Once I figured out what you have to return from get_drag_data for the scene editor to understand, it was easy.

Yeah, that does exactly what it needs to.
Can you explain what is happening here?

Yeah, godot's drag and drop us just a Control uses get_drag_data and when you drag over another control (like the scene) that gets is_drag_allowed (or something) called so it can checks if it knows what to do with the data we set in get_drag_data. Then there's another callback for when you actually release. Not sure how the spawn happens right away, so maybe I don't entirely understand.
Once I figured out how the scene editor's drop format (that dict with file paths), then it worked.
More details in my answer to myself: https://godotengine.org/qa/144475/how-can-implement-drag-and-drop-into-scene-from-editorplugin?show=144475#q144475

It even drops to the expected part of the scene tree (currently selected node), so it is consistent with everything else I did.


chore(vitest-angular): add vitest@2 to peerDependencies

PR Checklist

Closes #1249
What is the new behavior?
Supporting vitest version 2
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information
[optional] What gif best describes this PR or how it makes you feel?

Thanks! @allcontributors add @s0h311 for doc


Upstream master kflang

closes https://github.com/StatCan/kubeflow/issues/55
Something to think about: Do we want to merge upstream tasks into statcan/kubeflow master branch and then upstream from there or create draft PRs for upstream tasks, peer review and then send for upstreaming.

Closing PR. Upstream replaced ngx-translate with localize. Rather than rebasing this branch (conflicts), a new branch is created to rebase.


fix: change incorrect account deletion confirmation text

Description

Checklist

[ ] npm test runs as expected.
[ ] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

This should have been added to my first pr


Create Terraform provisioning for ECR

Will need to store the application somewhere to deploy it. It makes sense to use ECR to store the container for the application. Will need to look into how this will work though. There is a Docker Provider for Terraform so might be able to use that.

The registry now seems to be fine. Running into strange issues with building the conatiner though. Assuming it is from the context. Should probably move the app code and dockerfile in its own directory and reference that instead. Not sure if it just doesnt like the dots.

Still doesnt like anything I do with the context/Dockerfile

Need to verify but it seems that moving the application directory under terraform allowed the registry task to find and build it finally. Sigh

The issue was the /tmp dir with noexec. Having that set killed everything regardless of where the application directory was. I think I will still keep the app dir since it keeps everything organized.


Add checks in chaos-based tests to confirm actual fault/failure injection

Is this a BUG REPORT or FEATURE REQUEST?
FEATURE REQUEST

What happened:
Currently, failures are being injected in chaos-based tests using tools such as pumba, kubectl etc., It would be of value to "confirm" the faults were actually injected, using certain mechanisms - such as restart counts, deployment resource versions etc., which are impacted by the chaos.
This is especially helpful in trusting the results when litmus suites are executed in an automated manner in CI pipelines.

@ksatchit We have checks implemented for restart counts, resource versions for different chaos tests. Would you like to take a call on this issue if this can closed?

Implemented checks for restart counts, resource versions for different chaos tests.


Passing empty array

Likely missing check for empty array in Decrypt String (and possibly other) method.
Passing empty encrypted array causes assertion failed.
Empty Encrypted Log.txt
Passing empty public/private key array to Decrypt String method causes fatal error.
Empty Key Log.txt

Bug fixed by @Whiz652


Oracle constraint,references and foreign key views no longer work in 6.0.5

System information:

Operating system (distribution) and version
Mac OSX 10.14.4
DBeaver version
6.0.5
Java version
Openjdk 11.0.1
Additional extensions
None

Connection specification:

Database name and version
Oracle Database 11g Enterprise Edition Release <IP_ADDRESS>.0
Driver name
Oracle
Do you use tunnels or proxies (SSH, SOCKS, etc)?
No

Describe the problem you're observing:
After upgrading to 6.0.5 Constraint, foreign key and reference views no longer work when checking table properties.
When the client is searching for the constraints it fails with the following error:

SQL Error [904] [42000]: ORA-00904: "C"."CONSTRAINT_NAME": invalid identifier
ORA-00904: "C"."CONSTRAINT_NAME": invalid identifier
ORA-00904: "C"."CONSTRAINT_NAME": invalid identifier

The query that the client is using according to the query manager:
SELECT
    c.TABLE_NAME,
    c.CONSTRAINT_NAME,
    c.CONSTRAINT_TYPE,
    c.STATUS,
    c.SEARCH_CONDITION,
    (
        SELECT LTRIM(MAX(SYS_CONNECT_BY_PATH(cname || ':' || NVL(p,1),','))    KEEP (DENSE_RANK LAST ORDER BY curr),',')
        FROM   (SELECT
                       col.CONSTRAINT_NAME cn,col.POSITION p,col.COLUMN_NAME cname,
                       ROW_NUMBER() OVER (PARTITION BY col.CONSTRAINT_NAME ORDER BY col.POSITION) AS curr,
                       ROW_NUMBER() OVER (PARTITION BY col.CONSTRAINT_NAME ORDER BY col.POSITION) -1 AS prev
                FROM   ALL_CONS_COLUMNS col
                WHERE  col.OWNER =:owner AND col.TABLE_NAME = :tableName AND col.CONSTRAINT_NAME = c.CONSTRAINT_NAME
                )   GROUP BY cn CONNECT BY prev = PRIOR curr AND cn = PRIOR cn START WITH curr = 1
        ) COLUMN_NAMES_NUMS
FROM
    ALL_CONSTRAINTS c
WHERE
    c.CONSTRAINT_TYPE <> 'R'
    AND c.OWNER = :owner
    AND c.TABLE_NAME = :tableName

This seems to be caused by the inner join between ALL_CONS_COLUMNS and ALL_CONSTRAINT done in the select.
When downgrading to 6.0.4 which has the old query for constraints which does not include the changes from #5878 everything works as it should.
Steps to reproduce, if exist:
Trying to access Constraints, Foreign Keys or References from table properties in version 6.0.5

Duplicate of #5957
Thanks for the report anyway


UG update

Codecov Report
Base: 68.52% // Head: 68.52% // No change to project coverage :thumbsup:

Coverage data is based on head (8c9bd05) compared to base (9125adc).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #194   +/-   ##
=========================================
  Coverage     68.52%   68.52%
  Complexity      505      505
=========================================
  Files            86       86
  Lines          1614     1614
  Branches        157      157
=========================================
  Hits           1106     1106
  Misses          450      450
  Partials         58       58

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

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


Header cleanup

Hey @alexmorris , this one needs rebasing there's a merge from Master to the branch.


Small typo in MG

In the first sentence of section 4 of the MG generated by Drasil, the opening quotation mark around "information hiding" is actually a closing quotation mark, as can be seen in the image below. This is an automatically generated sentence so it is not specific to any one example.

Fixed in commit a7cc58a


Creating a stack with a cifs volume in portainer does not keep options

Bug description
Trying to create a stack containing a CIFS volume does not work within the portainer stack templates.
When trying to run the template / docker-compose.yml file, from the command line (docker-compose up) it works. However the exact same file does not work using the stack interface. The volume driver options are not taken into account.
Expected behavior
Expect the driver options to be taken into account
Steps to reproduce the issue:

Go to 'Stacks'
Click on 'Add Stack'
Select 'Web editor'
create a template like following:

---
version: '2.4'
services:
  emby:
    image: emby/embyserver:latest
    container_name: embyserver
    # runtime: nvidia # Expose NVIDIA GPUs
    network_mode: host # Enable DLNA and Wake-on-Lan
    environment:
      - UID=1000
      - GID=1000
    volumes:
      - /tmp/emby:/config
      - lacie-media:/mnt/data # Media directory
    ports:
      - 8096:8096 # HTTP port
      - 8920:8920 # HTTPS port
    restart: unless-stopped

volumes:
  lacie-media:
    driver: local
    driver_opts:
      type: "cifs"
      device: "//<IP_ADDRESS>/media"
      o: "username=pi,password=password,vers=2.1,uid=1000,gid=1000"

Deploy the stack.

Once deployed, the "lacie-media" volume does not have the options in portainer. ie. it does not work and connect to cifs.
Where-as when running the following file as a docker-compose.yml file, using docker-compose up, it works.
Technical details:

Portainer version: 2.1.1
Docker version (managed by Portainer): Docker version 20.10.3, build 48d30b5
Platform (windows/linux): linux

Ticket update by Bala Natarajan<EMAIL_ADDRESS>Hi
please change the version to 3.8 and try
version: '2.4' to  version: '3.8'

Running community edition ... version 3 not supported ...

Ticket update by Bala Natarajan<EMAIL_ADDRESS>Hi
I tried below , its getting deployed properly. pl try once. are you using any
extensions.
version: '3.8'
services:
  emby:
    image: emby/embyserver:latest
    container_name: embyserver
    # runtime: nvidia # Expose NVIDIA GPUs
    network_mode: host # Enable DLNA and Wake-on-Lan
    environment:
      - UID=1000
      - GID=1000
    volumes:
      - /tmp/emby:/config
      - lacie-media:/mnt/data # Media directory
    ports:
      - 8096:8096 # HTTP port
      - 8920:8920 # HTTPS port
    restart: unless-stoppedvolumes:
  lacie-media:
    driver: local
    driver_opts:
      type: "cifs"
      device: "//<IP_ADDRESS>/media"
      o: "username=pi,password=password,vers=2.1,uid=1000,gid=1000"

How can you deploy the above and confirm that it works ?
Have you set up an SMB network share on <IP_ADDRESS> / media ?
Whilst I agree the stack gets the deployed. The volume on the other hand also gets deployed but does not keep the driver_opts settings, and as such, does not leverage the SMB share, but simply creates a dummy local volume called lacie-media.

Ticket update by Bala Natarajan<EMAIL_ADDRESS>Hi
please let us know if the volume,container created with docker command works
fine. is it standalone node or a swarm cluster
pl find example below
docker volume create \
--driver local \
--opt type=cifs \
--opt device='//<IP_ADDRESS>/media' \
--opt o='username=pi,password=password,vers=2.1,uid=1000,gid=1000' \
lacie-media
docker run -it --rm -v lacie-media:/mnt/data -d --name samba-client alpine
bash

As per my initial message, it works directly with command line: "from the command line (docker-compose up) it works".
So, YES it works with command line.
NO it does not work using a compose file INSIDE Portainer

Hi teuteuguy,
I can not re-produce the issue.
I've tested by deploying the below stack.
version: '3.2'
services:
  httpd:
    image: httpd:latest
    networks:
        - httpd-network
    deploy:
        mode: replicated
        replicas: 1
    volumes:
      - lightnin_share:/usr/local/apache2/htdocs/
    ports:
      - "8080:80"
networks:
  httpd-network:
    driver: overlay
    attachable: true
volumes:
  lightnin_share:
    driver: local
    driver_opts:
      type: "cifs"
      device: "//<IP_ADDRESS>/smb"
      o: "username=xxxxxxx,password=xxxxxxx,vers=3.0"

Service deployed as below

Volumke Attached on the Container

Test file created in windows on the share

Shows up in the container as expected

Hi Samdulam
I don't knwo how you managed to run this, because when I try with similar settings, the stack comes back with an error:
"compose file version 3 is not supported"
I run portainer-ce version 2.1.1 on a raspberry pi, and I'm controlling another device via the portainer-agent.

version 3 as I'm deploying to docker swarm cluster. Below worked for a standalone docker env
version: '2.'
services:
  httpd:
    image: httpd:latest
    environment:
      - UID=1000
      - GID=1000
    deploy:
        mode: replicated
        replicas: 1
    volumes:
      - lightnin_share:/usr/local/apache2/htdocs/
    ports:
      - "8080:80"
volumes:
  lightnin_share:
    driver: local
    driver_opts:
      type: "cifs"
      device: "//<IP_ADDRESS>/smb"
      o: "username=xxxxxxx,password=xxxxxxx,vers=3.0,uid=1000,gid=1000"

I have tried your exact file. Does not work. Same result. The volume gets created but not as a cifs / samba mount.
Again, I'm trying to deploy this on a remote device via the agent.
Will try on the master device

Just tried on the master, same result.
Heres my stack:
`
version: '2.'
services:
httpd:
image: httpd:latest
environment:
- UID=1000
- GID=1000
volumes:
- lacie-media-test:/usr/local/apache2/htdocs/
ports:
- "8100:80"
volumes:
lacie-media-test:
driver: local
driver_opts:
type: "cifs"
device: "//<IP_ADDRESS>/media"
o: username=xxxxxxxx,password=xxxxxxxxxx,vers=2.1,uid=1000,gid=1000
`
Same result.

This is my volume

And I can see the files in the windows folder and inside the container mount.
Did you check if you can see the folder and files etc from the container and the share?
What about docker volume inspect on the volume?

I cannot see the files no. The folder is created locally on the disk and contains index.html, but its located on the host, not on the samba share.
Only way i've managed to get it to work, is by manually creating the volume via the portainer interface, not programatically via the compose file.

@teuteuguy Did you install the docker engine prior to installing portainer using snap? i.e. (sudo snap install docker). If I'm not mistaken, docker with snap maps docker volumes deep in the /var directory Full UNC /var/snap/docker/common/var-lib-docker/volumes. Thus manual volumes might not be accessible. If its a design requirement for you to manually create docker, you need to uninstall docker from snap and purge, re-install using the docker repo and you should have access. Otherwise, you can always create CIFS volumes in portainer and map them in individual containers, or reference them within a stack deployed by a docker-compose file. Hope it helps.

@Chiller2019
Can you post the following:
[1] Version of Portainer
[2] Portainer install command
[3] Your environment; Docker Standalone, Swarm, etc..?
[4] Stack code
Thanks!

@Chiller2019
Can you post the following:
[1] Version of Portainer [2] Portainer install command [3] Your environment; Docker Standalone, Swarm, etc..? [4] Stack code
Thanks!

Sure:

CE 2.15.1
docker volume create portainer_data docker run -d -p 8000:8000 -p 9443:9443 --name portainer \  --restart=always \  -v /var/run/docker.sock:/var/run/docker.sock \  -v portainer_data:/data \  portainer/portainer-ce:latest
Docker Standalone
Not with a Stack, just GUI, https://github.com/paperless-ngx/paperless-ngx/discussions/1572 and https://github.com/paperless-ngx/paperless-ngx/discussions/887

Manually adding a CIFS volume via the Portainer Web UI does work.
There is 1 missing piece in the options : addr=<server>
You can test this by creating a volume using the pre-defined CIFS options, then look at the volume details on the host under /var/lib/docker/volumes/<volume_name>/opts.json
{
"MountType":"cifs"
"MountOpts":"addr=<server>,username=<username>,password=<password>,vers=3.0"
"MountDevice":"//<server>/<share>"
"Quota":{"Size":0}
}

You need to add the server both as addr and as part of the share name!
The following works perfectly allowing read and write with mapped UID and GID :
Driver
Local
Driver options
type : cifs
o : addr=<server>,username=<username>,password=<password>,vers=3.0
device : //<server>/<share>

Also if you want to provide Domain auth, that must go into the CIFS options too
o : addr=<server>,domain=<domain>,username=<username>,password=<password>,vers=3.0

Hi,
It seems I'm encountering the exact same issue as the original poster. In my case, I'm getting the following error:
Failure
failed to deploy a stack: Container redis-dm-dev Creating Container nextclouddb-dm-dev
Creating Error response from daemon: failed to mount local volume:
mount //<IP_ADDRESS>/volume1/docker/nextcloud-redis-dm-dev:/var/lib/docker/volumes/nextcloud-dm-dev_redis-dm-dev/_data, data:
addr=192.xxx.xxx.xxx,username=nas_username, password=nas_password,uid=1000,gid=1000,vers=3.0: operation not supported

I'm using Portainer CE version 2.18.3. I installed Portainer using the following command:
sudo docker pull portainer/portainer-ce:latest
(I ran the install_portainer.sh shell script from this repository).
My Docker standalone version is 24.0.5.
Here is the link to the stack code: Stack code link.
Thanks,

I have the same issue


Version updates

@homu is active on the project now.  I had checked the setting for it to keep the history linear, but I think I might prefer to have merge commits (for a repo like this one).  Regardless, changes look good and your commits have been rebased onto the tree  Thanks!


Intellisense not working properly with bound functions

In general intellisense works just fine, see the following trivial example:
]
Intellisense suggests both the 2 members of "this", as expected.
However when using a bound function, the handler of the setTimeout method in this case, intellisense is unable to scope "this" to the class. It suggests nothing:

We can give a hint to intellisense, afterwards it comes up with the correct suggestion:

The real issue is when refactoring, find all references does not properly work:

This issue was moved to Microsoft/TypeScript#6713


Mingw build

I was unable to build Beast as-is with MinGW and MSCV. This PR makes it possible
Tested with MINGW 6.2 x64, and MSVC 2015 x64, Windows 7

Current coverage is 98.11% (diff: 100%)

Merging #86 into master will increase coverage by 0.04%

@@             master        #86   diff @@
==========================================
  Files            71         71
  Lines          4036       4033     -3
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           3958       3957     -1
+ Misses           78         76     -2
  Partials          0          0

Powered by Codecov. Last update 2f9a844...c5b0c7f

Coverage increased (+0.05%) to 98.116% when pulling c5b0c7fe647b5220e200fd9833bf9de783826586 on e-fominov:mingw_build into 2f9a8440c2432d8a196571d6300404cb76314125 on vinniefalco:master.

Thanks! This looks very promising, although realistically I have no way to test it since I don't use MinGW. Is there some way to have MinGW as a target on Travis?

I dont have much experience with Travis. MinGW itself is GCC-based and there will be no syntax differences, except the libc is missing on MinGW.
MinGW has cross-compiler that can be installed into Linux platform and also I found one stackoverflow post where it seems possible to use MinGW with Travis: http://stackoverflow.com/questions/28155308/how-to-cross-compile-with-mingw-on-linux-for-windows

Hmm...unfortunately these changes break 64-bit MSVC builds and I'm not sure why. This is the command line I used to build the solution and project files after cherry-picking your commits:
cd bin64
cmake -G"Visual Studio 14 2015 Win64" ..

I think I see what's happening. These are the lines causing problems:
find_package(Boost REQUIRED COMPONENTS coroutine context thread filesystem program_options system)
link_directories(${Boost_LIBRARY_DIRS})
link_libraries(${Boost_LIBRARIES})

Unfortunately with MSVC, we can't use the package finder to set the library directories, because there is no way to distinguish between 32 versus 64 bit builds. What I do is add a path to the Boost 32 bit libraries in the Microsoft.Cpp.Win32.user property sheet, and add a different path to the Boost 64 bit libraries in the Microsoft.Cpp.x64.user property sheet. If we were to use find_package and link_directories for this, then targeting both 32 and 64 bit builds in separate solutions would no longer be possible.
These are the steps I use to generate the separate solutions, please try them and see if they work with your changes:
cd bin
cmake ..
cd ../bin64
cmake -G"Visual Studio 14 2015 Win64" ..

Do you have boost compiled for x64?   I have tested this PR with MSVCx64 - compiles well. But my boost is compiled for x64
Looks like D:\lib\boost_1_61_0\stage\lib\ libraries on your machine are x86
This problem is because your original CMakeLists.txt file had no find_module(Boost) for Win32 compilation. Looks like you have something in your System Environment variables that makes it find boost in incorrect place. Normally CMake's findboost module searches it in c:\boost
Now it tries to find boost and finds it in D:\lib\boost_1_61_0\stage\lib, which contain x86 libraries
To make it use Boost from other folder, its possible to pass additional params to cmake:
cd bin64
cmake -G"Visual Studio 14 2015 Win64" .. -DBOOST_INCLUDEDIR=d:\boost64\include -DBOOST_LIBRARYDIR=d:\boost64\lib

I have 32-bit boost libraries in D:\lib\boost_1_61_0\stage and 64-bit boost libraries in d:\lib\boost_1_61_0\stage64. I also have $BOOST_ROOT set to /d/lib/boost_1_61_0/.
You're telling me that I should manually specify the header include and library include paths every time I want to rebuild the visual studio project files?

I tried this line with your changes:
cmake -G"Visual Studio 14 2015 Win64" .. -DBOOST_INCLUDEDIR=D:\lib\bo
ost_1_61_0 -DBOOST_LIBRARYDIR=d:\lib\boost_1_61_0\stage64

But the Additional Library Directories under Linker properties shows
D:/lib/boost_1_61_0/stage/lib;D:/lib/boost_1_61_0/stage/lib/$(Configuration);%(AdditionalLibraryDirectories)

Try adding -DBoost_NO_SYSTEM_PATHS=ON
What is the version of CMake you are using? If your version < 3.6.2, it may not know about boost version 1.61. You can tell him that this version exists:
-DBoost_ADDITIONAL_VERSIONS=1.61

I have just checked out master branch CMakeFiles.txt, and MSVC told me that he cant compile:
C:\work\Beast\include\beast/core/detail/ci_char_traits.hpp(11): fatal error C1083: Unable to open include file: boost/range/algorithm/equal.hpp: No such file or directory (compiling C:\work\Beast\test\http\parser_bench.cpp) [C:\work\Beast\b15\test\http\bench-tests.vcxproj]
...

Are you sure, it was compiling with previous version of CMakeFiles.txt?

I'm on CMake 3.6.0. I will try updating it.
Yes, I am sure that the tip of master compiles with CMake. I do all of my development in Visual Studio and I use CMake to generate the project files. You need to add the include path and library path to your Microsoft.Cpp.x64.user property sheet (View -> Property Manager).

Updating to CMake 3.6.2 had no effect on the result, I get the same errors. This is the command line I used:
cd bin64
rm -rf *
cmake -G"Visual Studio 14 2015 Win64" .. -DBOOST_INCLUDEDIR=D:\lib\boost_1_61_0 -DBOOST_LIBRARYDIR=d:\lib\boost_1_61_0\stage64

This is what the linker properties on the resulting project look like:

I have restored original code for MSVC compilation process. MinGW compiles well on my pc
To compile MSVC I need to open .vcproj in Studio and set directories manually

Coverage increased (+0.05%) to 98.116% when pulling 0711d3b2d80c23e148c73d4d8ce834fabf2316b3 on e-fominov:mingw_build into 2f9a8440c2432d8a196571d6300404cb76314125 on vinniefalco:master.

This works for me now:
https://github.com/vinniefalco/Beast/commits/mingw
It will go into b14, so I'll close this. Thanks for your contribution!


JS Clock project added

Added an analog clock javascript mini project

add your name in CONTRIBUTING,md file


make it support css

webpack:
{
plugins: [
new HtmlWebpackPlugin(),
new InlineChunkHtmlPlugin(HtmlWebpackPlugin, [/.(js|css)$/]),
]
}

Does this fix an issue? What is the issue exactly?

@ianschmitz this allows css assets to be inlined. Currently on js files are inlined as only script is supported.


Add WrapOption to OperatorWrap to change detected style easily after running once

What's changed?
Add WrapOption wrapOption to OperatorWrap, and change from a static visitor to an inline visitor. The actual code changes are a lot smaller when ignoring whitespace.
What's your motivation?
Projects often rely on detection, or the default which matches CheckStyle. Yet when you want to change or enforce a new standard, it's cumbersome to have to configure a style for every project when you just want to change what's used once, and henceforth rely on detected style again.
Have you considered any alternatives or workarounds?

Continue to ask folks to configure an explicit style.
Accept the CheckStyle default of operators on next line.

Should we make it more convenient to supply style config when running recipes? Just so that we don't en up sprinkling convenience style options all over the place.

That might be a good idea, as I'm indeed not a fan of sprinkling options, even if the alternative is cumbersome. Not quite sure what making it easier would like though.
I did notice we also have a copy of this recipe in rewrite-static-analysis, so I'll move this change there for now, and remove the recipe here, as there's no apparent references elsewhere at this point in time.
https://github.com/openrewrite/rewrite-static-analysis/blob/main/src/main/java/org/openrewrite/staticanalysis/OperatorWrap.java


Added release process to README.md.

Proposed changes
Describe the use case and detail of the change. If this PR addresses an issue on GitHub, make sure to include a link to that issue here in this description (not in the title of the PR).
Checklist
Before creating a PR, run through this checklist and mark each as complete.

[ ] I have read the CONTRIBUTING doc
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked that all unit tests pass after adding my changes
[ ] I have updated necessary documentation
[ ] I have rebased my branch onto main
[ ] I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

Hi @pammecrandall
With this commit https://github.com/nginxinc/nginx-kubernetes-gateway/commit/7d523ae4e34251522671524b172c9edd5a4bce42 , the docs now are in a separate folder, rather than in the readme.
Could you put the release process content in a separate file in the docs folder? For example, release-process.md.

Could you put the release process content in a separate file in the docs folder? For example, release-process.md.
Sure!  I'll make that change now.


Issue on downloading chromnium

As title, the log is attached.
Thanks for taking a look!

I have the same issue

Does anybody please have any idea, how to solve this? Thank you!

@imakou @gelbxx  please clone the latest version. Selenium driver issue has been fixed.

the above error is resolved but it still shows an error

@gelbxx Make sure you have selenium==4.11.2 and webdriver-manager==4.0.0 installed. Even though you pull the latest version, it would still have the old versions of selenium and webdriver-manager installed in your python environment. Let me know if this is the case.


Wrong warning when a saved model (from TF2.4) is loaded using tf-nightly

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): pip
TensorFlow version (use command below): TF2.4, tf-nightly
Python version:
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:

Describe the current behavior
Using TF2.4, a Keras model was saved using model.save.  Later, when I tried to load the saved model using  tf-nightly, code throws unexpected error as shown below.
2.5.0-dev20210112
WARNING:tensorflow:SavedModel saved prior to TF 2.4 detected when loading Keras model. Please ensure that you are saving the model with model.save() or tf.keras.models.save_model(), *NOT* tf.saved_model.save(). To confirm, there should be a file named "keras_metadata.pb" in the SavedModel directory.
WARNING:tensorflow:No training configuration found in save file, so the model was *not* compiled. Compile it manually.

Describe the expected behavior
The following warning should be revised as the initial model was saved using TF 2.4 but warning complains that the model was saved prior to TF 2.4.
WARNING:tensorflow:SavedModel saved prior to TF 2.4 detected when loading Keras model. Please ensure that you are saving the model with model.save() or tf.keras.models.save_model(), *NOT* tf.saved_model.save(). To confirm, there should be a file named "keras_metadata.pb" in the SavedModel directory.
The above warning was noticed only when the model was saved in tf format. The above warning doesn't appear when the model was saved in h5 format.
Standalone code to reproduce the issue
Please check the gist here.
Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.
This issue was originally opened earlier here

@jvishnuvardhan
I have tried in colab with saving the model in TF 2.4 and loading the model in TF nightly version(2.5.0-dev20210113)  was able to reproduce the issue.Please, find the gist here.
However If i save and load the model in TF nightly version (2.5.0-dev20210113) gist here or If i ave the model and load the model in TF 2.4 version gist here then i am not seeing the below error message .
WARNING:tensorflow:SavedModel saved prior to TF 2.4 detected when loading Keras model. Please ensure that you are saving the model with model.save() or tf.keras.models.save_model(), *NOT* tf.saved_model.save(). To confirm, there should be a file named "keras_metadata.pb" in the SavedModel directory.
Thanks!

@jvishnuvardhan
I have tried in colab with saving the model in TF 2.4 and loading the model in TF nightly version(2.5.0-dev20210113)  was able to reproduce the issue.Please, find the gist here.
However If i save and load the model in TF nightly version (2.5.0-dev20210113) gist here or If i ave the model and load the model in TF 2.4 version gist here then i am not seeing the below error message .
WARNING:tensorflow:SavedModel saved prior to TF 2.4 detected when loading Keras model. Please ensure that you are saving the model with model.save() or tf.keras.models.save_model(), *NOT* tf.saved_model.save(). To confirm, there should be a file named "keras_metadata.pb" in the SavedModel directory.
Thanks!

This is intended behavior and the warning is to encourage users to use model.save  instead of tf.saved_model.save when saving keras models.
Here is a gist where model was trained and saved using TF2.4. Then, loaded the model using tf-nightly and trained again on the same data. The accuracy with TF2.4 and tf-nightly are similar which shows that there is no problem loading the model using tf-nightly. Thanks!

Hi @jvishnuvardhan , there is no keras_metadata.pb in tf2.4 saved_model dir. But in tf2.5, I found keras_metadata.pb.
Do you know what's the point of keras_metadata.pb?
Is it compatible with prior tf version that has no keras_metadata.pb?

In TF 2.5.0 model.save("model_dir") creates one additional file in the model folder - keras_metadata.pb.
The difference btw prev versions is that now we can load the model back and get fully-featured Keras model.
model=tf.keras.models.load_model("model_dir")
type(model)
# tensorflow.python.keras.engine.sequential.Sequential

model._is_graph_network
# True

model.summary() # Works!

We can even re-fit the model!
We can save it in h5 format (some tools, such as Netron, support only h5 format)

In TF 2.5.0 model.save("model_dir") creates one additional file in the model folder - keras_metadata.pb.
The difference btw prev versions is that now we can load the model back and get fully-featured Keras model.
model=tf.keras.models.load_model("model_dir")
type(model)
# tensorflow.python.keras.engine.sequential.Sequential

model._is_graph_network
# True

model.summary() # Works!

We can even re-fit the model!
We can save it in h5 format (some tools, such as Netron, support only h5 format)

@apivovarov Hi, thanks for the reply.
So if we use load_model() in tf2.5, the states of optimizer will be restored automatically.
However, we need to use custom_objects in tf2.4 if we have used some custom layers.
And if we want to deploy the saved model in tf2.5, we can simply delete the keras_metadata.pb to reduce the file size, and everything will remain the same as tf2.4.
Please correct me if there is any mistakes!

Suppose I am past the point of no return and I cannot follow the "encouragement" of this warning. How do I suppress it?


Learning with GPU docs

It's unclear how does GPU/TPU support work in swift for tensorflow. I haven't found any docs on this topic.
In PyTorch I am able to cast some tensor from cpu to gpu by calling special method .to(device) like x.to(t.device("cuda:2")) in order to cast x to gpu with id equal to 2.
How does this work in swift for tf? I noticed that I could change env variable in collab from None to GPU and all computations would be performed on GPU, but it's still unclear how could I do something like that using compiler.
I believe that learning models with GPU/GPUs is very important part of deep learning pipeline and thus it have to be in docs in any form.

Currently, device placement in Swift for TensorFlow (and TensorFlow in general) is per-operation, not per-tensor. You can use the withDevice(_:_:perform:) API (implemented here) to switch between devices. You can switch between CPU and GPU for parts of your program using this API. If you have installed a CUDA-enabled toolchain on Linux and already have a GPU installed, the default device should already be the GPU.
While the device placement API is available in API documentation, it is true that it's not documented in any of our tutorials. That is because device placement is still an experimental feature that does not yet work reliably. For instance, the tpu case in the DeviceKind enum is not supported yet. We plan to add tutorials once the feature becomes more ready and reliable.


Fastq summary displaying incorrectly

When viewing the html summary of fastq files on Qiita, parts of the quality scores are sometimes cut off by new sequence headers on the same line. The problem seems to occur because the < symbol is used in fastq quality scores, which is misinterpreted when it is displayed in html.

Being fixed in https://github.com/qiita-spots/qtp-target-gene/pull/25


Recover documentation test

I think the PR #386 by @zyzhu disabled the documentation tests to get things to work. It would be nice to re-enable this at some point.

I commented them out as the old documents tests has the following errors. For instance.
./frame.fsx (1:0-957:13): Error - An implementation of the file or module 'Frame$fsx' has already been given
Do you know anything about this error? I saw a similar error in Fable issues related to diamond dependencies.
https://github.com/fable-compiler/Fable/issues/639

@tpetricek I've recovered the documentation tests by working around the above error. Do you think it is ok?
https://github.com/fslaborg/Deedle/pull/390


Can Dolby vision auto mixing be added

Can Dolby vision auto mixing be added

call mp4box to mux?


No scipy-1.9.1-cp310-cp310-win32.whl found on PyPi

Is your feature request related to a problem? Please describe.
I need a 32 bit version for windows. And non is available on PyPi.
Describe the solution you'd like.
No response
Describe alternatives you've considered.
No response
Additional context (e.g. screenshots, GIFs)
No response

Sorry, no 32 bit wheels are available on windows, due to an incompatibility of 32 bit Fortran compilers with the new meson build system.  At the moment there is no real movement towards changing this situation, there's just not that much demand. Can you install an older wheel? Why is it necessary to install a 32 bit wheel?

Thanks for the answer, I am working with some legacy systems, which require python 32 bit. And we are currently using v3.10.. Maybe I can downgrade to 3.9.


Verify files to extract are under destination

We've been OK since we extract trusted archives (Cloud SDK zips) , but it's better to fix it correctly from the security point of view.
https://snyk.io/research/zip-slip-vulnerability#what-action-should-you-take
I've done actual installation on Linux and Windows.

I'll add tests for extracting actual zips that exploits this.

I'm not sure why the test fails on Mac. I'll have to push some temporary diagnostic commits to figure out what is happening.

Turns out /tmp was expanding to /Volumes/BuildData/tmpfs/ on Mac.

@koto CC'ed per Bug 109861633


When attempting to build using ng build platform -c development with the development configuration, the build process fails. This issue seems to be related to the usage of the native-federation-plugin.

Steps to Reproduce

Clone the repository with the specific branch:git clone -b native-federation https://github.com/dipu7388/multiple-entry.git
cd multiple-entry

Install dependencies:
npm install
Attempt to build using Angular CLI:
ng build platform -c development

Expected Behavior
The build process should be completed successfully, generating the output bundle(s) for the development configuration.
@manfredsteyer  can you please look into it.

@jogelin @manfredsteyer can we have update on this.

@dipu7388 in your angular.json file remove the "dev": true property from your configurations.
"configurations": { 	"development": { 		"target": "platform:esbuild:development" 	} },


[ISSUE #2743]Fix the problem cause by code(#2743)

Fix the problem cause by code(#2743)

Codecov Report

Merging #2949 (d9d97ef) into master (16f4fdc) will decrease coverage by 0.32%.
The diff coverage is 40.00%.

@@             Coverage Diff              @@
##             master    #2949      +/-   ##
============================================
- Coverage     59.79%   59.47%   -0.33%
+ Complexity     4463     4439      -24
============================================
  Files           691      695       +4
  Lines         20047    20069      +22
  Branches       1803     1807       +4
============================================
- Hits          11988    11936      -52
- Misses         7047     7122      +75
+ Partials       1012     1011       -1

Impacted Files
Coverage Δ

.../apache/shenyu/plugin/sentinel/SentinelPlugin.java
78.94% <33.33%> (-1.06%)
:arrow_down:

...ache/shenyu/plugin/httpclient/WebClientPlugin.java
83.33% <50.00%> (-2.72%)
:arrow_down:

.../apache/shenyu/admin/model/dto/BatchCommonDTO.java
50.00% <0.00%> (-7.15%)
:arrow_down:

...apache/shenyu/admin/model/dto/AuthPathWarpDTO.java
57.14% <0.00%> (-7.15%)
:arrow_down:

...org/apache/shenyu/admin/model/dto/AuthPathDTO.java
58.82% <0.00%> (-5.89%)
:arrow_down:

...che/shenyu/admin/service/impl/RuleServiceImpl.java
78.09% <0.00%> (-4.77%)
:arrow_down:

...che/shenyu/admin/model/vo/DashboardUserEditVO.java
60.86% <0.00%> (-4.35%)
:arrow_down:

...ache/shenyu/admin/model/dto/DataPermissionDTO.java
59.25% <0.00%> (-3.71%)
:arrow_down:

...rg/apache/shenyu/admin/model/page/CommonPager.java
44.82% <0.00%> (-3.45%)
:arrow_down:

...shenyu/admin/service/impl/SelectorServiceImpl.java
72.06% <0.00%> (-3.36%)
:arrow_down:

... and 35 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2fd6618...d9d97ef. Read the comment docs.

pls check ci

pls resolve conficts file


No error is shown when removing nonexistent file from archive

Hello,
When I remove a nonexistent file from an archive, I get Exiting with error due to previous error but no other errors are shown:
$ touch test1 test2 test3
$ tar -cf test.tar test1 test2 test3
$ exec r test.tar test4
Exiting with error due to previous error

5f5cd94ee2658e1c511502380ee961adf1544697 should fix this.

5f5cd94ee2658e1c511502380ee961adf1544697 should fix this.


feat: allow fields remapping in JSON logs

First stab at #750

@redbaron - would it be possible to document how this customization can happen? Thanks!

We discussed it during today's bi-weekly meeting and agreed we could move this forward and document this by adding it as a parameter to the cnpg subcommand generating installation manifests and the helm chart.

One idea we discussed in the dev meeting is to add those two options to the kubectl cnpg install generate command, and document this in:

the plugin page
the logging page - when we explain the format we could add a box that mentions that those two fields can be renamed

One idea we discussed in the dev meeting is to add those two options to the kubectl cnpg install generate command, and document this in:
* [the plugin page](https://cloudnative-pg.io/documentation/current/cnpg-plugin/#generation-of-installation-manifests)

* [the logging page](https://cloudnative-pg.io/documentation/current/logging/) - when we explain the format we could add a box that mentions that those two fields can be renamed

I've added box to the logging page. As for the generate command, these new flags are no more special than many existing flags. Generate command produces yaml, which system administrators can trivially edit to add more flags.

/ready-to-test

I realized the patch is not actually passing the mapping down to the cluster's pods, shouldn't be too hard, I'll try addressing that.

I switched defaults to empty string to be able to differentiate between default values and configured values to avoid triggering a restart of all running clusters upon upgrade.

/test

/ready-to-test

Thanks for pushing it!


Proposal for consolidated API response payload structure

Problem statement
We're sending back top-level arrays for collection-oriented responses (/deliveries and /submissions endpoints in particular), and we can update this to return an object so that we can include collection metadata like entity type and pagination information.
What you need to know

See this Slack conversation for more information.

Acceptance criteria

[ ] A proposal doc is reviewed and approved by Platform team

This is a more fundamental structural change that we want to have ironed out (between all teams) before we build/launch the STLT dashboard.

Awaiting review from Arnej


Random camera vertical shaking with Skyrim Outfit System SE Revived

It happens pretty randomly, so I don't really know how to reproduce it. When it happens, the issue persists even when my hands leave my mouse & keyboard. Also tested 3rd person view and vanilla 1st person view, and this issue didn't happen.
I haven't removed other related mods (nemethis, xpmse, HDT stuffs...) to find the root cause, but decide to post here to see if others have the same issue.

After a lot of trial and errors, I think the culprit is "Skyrim Outfit System SE Revived". It surprised me for I didn't think this mod would have problem with camera mods. The issue only happens when both mods are activated, but using one of the two mods don't have any problem.

I see a beta version got released yesterday, see if the issue persists with that one.
I find it abit odd how it would effect the camera though. When it occurs what happens if you go to third person then back to first does it still occur?

The issue still persists with the beta version.
The second method can't fix the issue either.

You can see if it stops doing that if you disable the head, another thing you can try if you have the menu loaded is whilst in first person change the Y to see if you spot anything odd.

Disabling head doesn't help.
By "change the Y", I think you want me to test in a weird 3rd person mode. In that mode, I can see my character shaking with camera in the same time. I don't really find other odd things
I also discover a similar/identical sympton when switching gears with unpaused menu mod "Skyrim Souls RE - Updated", and the shaking chance is 100% in this case. Not sure if it is related, but may worth a look.
Note: I also test the Skyrim Souls mod seperately, and it is unrelated to the random shake issue.


Add files via upload

Your checklist for this pull request
Author name
Author:
Jonas Hendrix
About your game
What is your game about?
You are in a Dungeon and you must find you way out. You need to find a way out of the dungeon.

How do you play your game?
use WASD to move. you well need to find key to unlock door to get to the exited.

Code
Check off the items that are true.

[x] The game was made using the Sprig editor.
[ ] The game is placed in the in the /games directory.
[ ] The code is significantly different from all other games in the Sprig gallery (except for games labeled "demo").
[ ] The game runs without errors.
[ ] The name of the file/game contains only alphanumeric characters, -s, or _s.
[x] The game name is not the same as the others from gallery

Image (If an image is used)

[ ] The image is in the /games/img directory.
[x] The name of the image matches the name of your file.

Thanks for your PR!

@Jonas07123 do you still wish to move this towards landing?  I played it and it seems to pass the guidelines that we have.

Great game! Congrats:)
If you're a teen, you can get your sprig here! http://hack.af/sprig-order
Hack Clubbers would love to see this! Just post a link and 1-2 sentences talking about your game to our #ship channel:)


Codecov security

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@093572d). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #74   +/-   ##
=======================================
  Coverage        ?   91.28%
=======================================
  Files           ?       42
  Lines           ?     3800
  Branches        ?        0
=======================================
  Hits            ?     3469
  Misses          ?      331
  Partials        ?        0

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 093572d...2ccf535. Read the comment docs.