Error runnig a frozen graph of the 128-dimensional embeddings model

I froze the new 128-dimensional embeddings model using the freeze_graph.py, but at the time of running the session, it gives this error:
Failed precondition: Attempting to use uninitialized value Bottleneck/BatchNorm/moving_variance   [[Node: Bottleneck/BatchNorm/moving_variance/read = Identity[T=DT_FLOAT, _class=["loc:@Bottleneck/BatchNorm/moving_variance"], _device="/job:localhost/replica:0/task:0/cpu:0"](Bottleneck/BatchNorm/moving_variance)]]
Should I change something in freeze_graph.py?

@mhaghighat
It has been discussed in #108.
The new bottleneck nodes should be added to the whitelist in freeze_graph.py:
if node.name.startswith('InceptionResnetV1') or node.name.startswith('embeddings') or node.name.startswith('phase_train') or node.name.startswith('Bottleneck'):

Thanks a lot, @ugtony.

@ugtony
with the updated freeze_graph.py I'm getting this KeyError:
Model directory: models/20170216-091149/ Metagraph file: model-20170216-091149.meta Checkpoint file: model-20170216-091149.ckpt-250000 Traceback (most recent call last):  File "freeze_graph.py", line 96, in <module>    main(parse_arguments(sys.argv[1:]))  File "freeze_graph.py", line 48, in main    saver = tf.train.import_meta_graph(os.path.join(model_dir_exp, meta_file), clear_devices=True)  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/saver.py", line 1526, in import_meta_graph    **kwargs)  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/meta_graph.py", line 502, in import_scoped_meta_graph    producer_op_list=producer_op_list)  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/importer.py", line 258, in import_graph_def    op_def = op_dict[node.op] KeyError: u'VariableV2'

@ugtony @mhaghighat
I'm getting this error with the new freeze_graph.py
Model directory: models/20170216-091149/
Metagraph file: model-20170216-091149.meta
Checkpoint file: model-20170216-091149.ckpt-250000
Traceback (most recent call last):
 File "freeze_graph.py", line 96, in <module>
   main(parse_arguments(sys.argv[1:]))
 File "freeze_graph.py", line 48, in main
   saver = tf.train.import_meta_graph(os.path.join(model_dir_exp, meta_file), clear_devices=True)
 File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/saver.py", line 1526, in import_meta_graph
   **kwargs)
 File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/meta_graph.py", line 502, in import_scoped_meta_graph
   producer_op_list=producer_op_list)
 File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/importer.py", line 258, in import_graph_def
   op_def = op_dict[node.op]
KeyError: u'VariableV2'

@RakshakTalwar,
It happened to me too. I updated to TensorFlow r1.0, and it worked.

@mhaghighat thanks for letting me know!

confirmed.
it doesn't work for tf0.12 but for tf r1.0.1


uid:// Paths Fail to Load at Editor Startup

Tested versions

Reproducible in v4.3.stable.mono.official [77dcf97d8]
Not reproducible in v4.2.2.stable.mono.official [15073afe3]

System information
Windows 11 v4.3.stable.mono.official [77dcf97d8]
Issue description
In Godot 4.3.0, when opening a project that loads a resource by a uid:// path at startup, the resource fails to load.
The attached MRP uses the following plugin script to load a resource at startup:
@tool
extends EditorPlugin

func _enter_tree():
	var uidPath = "uid://dr1hds7vve78t";
	var resPath = "res://resource.tres";
	var uidResource = ResourceLoader.load(uidPath);

	if uidResource == null:
		printerr("Resource is null, meaning it couldn't be loaded by uid:// path.")
	else:
		print("Resource could be loaded by uid:// path.")

	var resResource = ResourceLoader.load(resPath);

	if resResource == null:
		printerr("Resource is null, meaning it couldn't be loaded by res:// path.")
	else:
		print("Resource could be loaded by res:// path.")

With this, I get the following errors at startup:
Godot Engine v4.3.stable.mono.official (c) 2007-present Juan Linietsky, Ariel Manzur & Godot Contributors.
--- Debug adapter server started on port 6006 ---
--- GDScript language server started on port 6005 ---
  core/io/resource_uid.cpp:132 - Condition "!unique_ids.has(p_id)" is true. Returning: String()
  Resource file not found:  (expected type: )
  Error loading resource: 'uid://dr1hds7vve78t'.
  Resource is null, meaning it couldn't be loaded by uid:// path.
Resource could be loaded by res:// path.

This issue does not occur with the MRP using v4.2.2.stable.mono.official [15073afe3], so there seems to be a regression between 4.2.2 and 4.3.0.
I believe the issue in #95535 may be related.
Once the editor has fully started up, if you toggle the plugin to invoke the _enter_tree method again, Godot is able to successfully load the resource by uid:// at that point.
Steps to reproduce

Open the MRP in Godot 4.3.0.
The error should appear in the log. If it doesn't, enable the GdDummy plugin from the Project > Project Settings > Plugins tab.

Minimal reproduction project (MRP)
GodotUidBug-main.zip

Bisecting points to #92303 as the culprit:

CC @Hilderin


Edit previous messages with new spots

Summary
When a radio operator switches frequencies or modes and respots, SpotBot will post a new message reflecting that (depending on your HamAlert limits).
This can get a bit noisy - so instead let's edit the last message referring to this operator.
These docs describe what's needed to edit a message:
Identically to sending messages with webhooks you can edit previously sent ones. For that you need to have message id which can be copied with right-clicking on the message and selecting Copy Message ID from context menu (Developer Mode has to be enabled in user settings). Alternatively, id can be retrieved from response after webhook sending request (wait=true has to be present in query).

Request URL is https://discord.com/api/webhooks/123/w3bh00k_t0k3n/messages/456, where 456 is message id.

Request verb has to be set to PATCH instead of POST.

Request body is identical to the one we use for sending, but you have to consider next things:

Not providing content and embeds won't remove them from message, for that you have to pass empty string ("content": "") and array ("embeds": []) respectively.
Attachments will be appended instead of replaced, to remove all attachments pass attachments with empty array in value ("attachments": []). If you want some of them to persist provide them in the same attachments array (attachment objects have to be retrieved from previous edit or send responses)

Basic Design

we need to use the query param ?wait=true to get back the message id from the posted message
we need to store (perhaps in the Azure Table attached to the function app) the last message posted for a callsign
if the message is < N hours old (maybe 4?), we'll edit the message (PATCH) - perhaps with a newline? or perhaps just a complete rewrite?

https://learn.microsoft.com/en-us/python/api/overview/azure/data-tables-readme?view=azure-python


Exclude out of stock product

Would it be possible to only include product with quantity superior to 0 ?
It could be interesting to get a checkbox "Exclude product out of stock".
Even if it's not a feature that could be added could you tell me how I could acheive to modify this module to only add product that are actualy in stock ?

Thanks

This is bad for SEO.

Google win still index all your products even if the products that are out of stock is not in the sitemap.xml :-)


Fix incorrect usage of is_open in Python 3.

Greetings!
I am trying to port a project to Python 3, and am almost there... but it depends on the thrift_sasl module, and it appears that it assumes a change to the TTransportBase API which is not present in the Apache library. Namely, TTransportBase.isOpen does not seem to change to TTransportBase.is_open under Python 3. This patch fixes this.
Best,
M
@wesm : As you are the latest person to commit to the repository, can you maybe take a look?

Okay. This code assumes that one uses thriftpy (and not thrift) on Python3; even though the official libraries do support Python 3 now (or they seem to).

@matthewwardrop aw crap, I just made basically the same PR to fix this, didn't see yours. You had any progress on this? If not I might contact @laserson as they committed the original code?

Sorry about the delay on this. the @eddiejessup patch is a little more flexible (and works with thriftpy), so I'm going to accept that one and close this one, making a 0.2.1 thrift_sasl release. Thank you

No worries! Thanks!


Deploy command returns strange error when not logged in

Steps to reproduce:

try to redeploy a deployment when not logged in

The error message returned by the cli doesn't say anything about not authorized or login required.
$ bosh-go -e env deploy -d dummy dummy.yml
Using environment '<redacted-ip>' as anonymous user

Using deployment 'dummy'

Fetching diff result:
  Performing request POST 'https://<redacted-ip>:25555/deployments/dummy/diff?redact=true':
    Performing POST request:
      Post https://<redacted-ip>:25555/deployments/dummy/diff?redact=true: http: ContentLength=13729 with Body length 0

Exit code 1

This has been fixed as of the latest release. Please feel free to reopen if you have further questions.


Subcommands

Tools, which aren't a command in their own respect but rather offer several independent sub commands, are quite hard to achieve with the current state of the library. Examples are git or the windows service utility sc.
Subcommands are a good way to reduce the complexity of the commandline by separating different concerns.

What's the status on this? except for the use of the comma operator which seems a little weird, i for one really like it


feat: introduce gsuite addons

Tests are failing due to missing imports. We need to generate classes for these protos: https://github.com/googleapis/googleapis/tree/master/google/apps/script/type

Same as #5577, I suggest removing the GrpcClient.php classes, ignoring those classes in owlbot.py,  and adding the newline back for composer.json. Otherwise LGTM!

@bshaffer can you please take another look at this batch of new libraries? Thank you!


Package Update

Hi! I took some time to help, I have this package in use and I have been wanting to make some improvements for a long time.
They were basic changes:

SDK version
Documentation
README in Spanish

and more.

@OscarTinajero117 Thanks for PR, I am going through the code and testing it locally.


Tag v2.1.0

According to http://fgnass.github.io/spin.js/ the current version is 2.1.0 (released 2015-04-16). However, this release hasn't been tagged yet in the Git repository.

Thanks, fixed it!

Is this version is CSP compatible or not?
I am importing the spin.min.js V2.0.1 library file in my AngularJS with C# application. The problem arises when I add the following CSP line to my project:
`

I need to remove unsafe-eval from the policy. Therefore, I need to check whether the library file is CSP compatible or not, specifically checking if setTimeout, is used without causing errors in the console.


Fix unexpected permission validation test fail

Test might fail due to unexpected order of categories in remoteProvider.listCategories()

Landed in https://github.com/metarhia/globalstorage/commit/8b886fa94d431420dc5179957db44432b0f7ed8f.


Upgrade to 2.18 and remove jquery usage

Still got some work to do here.  Previous implementation for scroll listeners did something to the effect of scroll.elementId whereas now it just simply listens for scroll.  Need to look into if this could break anything.

[x] upgrade to 2.18 (before 3.0 release)
[x] replace usage of jquery
[ ] check for regressions
[ ] properly remove jquery.

Closes #118

I'm getting Uncaught DOMException: Failed to construct 'IntersectionObserver': rootMargin must be specified in pixels or percent. When trying out the branch -> this is due to _viewportTolerance.left and .right being undefined. (newest desktop Chrome emulating  Nexus 6p).

@bkoval What do you have set for the viewportTolerance, if anything?  The browser automated tests aren't showing anything.  Just tried this branch out as well on 4200.
Note: one thing I did notice is that we aren't allowing users to specify %'s for the viewport tolerance 😱
https://github.com/DockYard/ember-in-viewport/blob/master/addon/mixins/in-viewport.js#L104

@snewcomer I am just setting top and bottom. Could it be that on master ember-in-viewport uses defaults in such case?

@bkoval would you mind pasting your viewportTolerance config?

Sure:
const viewportTolerance = 1000;

this.set('viewportTolerance', {
    top: viewportTolerance,
    bottom: viewportTolerance
});

@bkoval Welp, you are completely correct.  Sry about that.  Put a PR in to fix.  In the meantime, if your config looked like this, it should work.  Thanks for reporting this bug!
this.set('viewportTolerance', {
    top: viewportTolerance,
    bottom: viewportTolerance,
    right: 0,
    left: 0
});

Tested this branch out on our app and works 👍 .  Anybody else wanna give it a go?


Issue with indeterminate results using image_url

https://github.com/igas/faker/blob/42c1e36a4d8420ce05133dc8905cd3b178d79b24/lib/faker/internet.ex#L95
needs to be corrected to
defp image_url(0), do: "https://placekitten.com/#{:crypto.rand_uniform(1, 1024)}x#{:crypto.rand_uniform(1, 1024)}"

Hi @lackdaz and @sotojuan,
I've just checked their website http://placekitten.com/ and according to the example it's correct URL, but I couldn't load any images.
Can you please check from your side? Maybe we need to drop this one.

I've checked and it is indeed working. My bad and will drop the issue

And I will close my PR.


Works on Thunderbolt Display with Mac Pro (El Capitan)

Great library! Just letting you know that it's working for me on a thunderbolt display connected to a mac pro running El Cap via thunderbolt cable.

Thanks! Glad to know as I have not had a chance to test it on a Thunderbolt display.


Null value in "more options"

This issue is imported from pivotal
See screenshot. Fixed and committed, however no new release is made yet (will be done when all stories are tested and rework is done).

(Okke Harsta - Nov 2, 2022)


Psionics (general support)

Create support for psionics. Much like spells, but have different fields.
Will be placed in a submenu undres SPELLS main menu.

I made a first attempt, copied all the spells and replacing spell with power ;-)
seperate issue
It's a lot of work, perhaps we could also work on some kind of community database exchange to ease the chore of data entry?


trailingPeriod setting not honored on subdomains

Currently if I try to run urlRegexSafe on a string like 'http://www.google.com.' it will return 'http://www.google.com' as the first match but if I were to run it on 'http://www.google.com/subdir.' it will return 'http://www.google.com/subdir.' (trailing period included).  Is this the intended functionality?  How can I go about ensuring that trailing periods will always be ignored?

+1

PR welcome!

Can you submit a PR and maybe a test? @birtles would love to get this in

Sure, I've submitted #29 for this.

Thank you! 🙏


fix: bug 1697 - switch timestamp logic to consider span, not calendar days

Requested feature change; display HH:MM if the timestamp is less than 24 hours difference for timestamps

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Delete Priority.none

PR for #139
Refactored Priority.Type to Priority.Level and parseXmlString to valueOf for readability.

Coverage increased (+0.1%) to 90.534% when pulling 3ea1aa6106b3ee78e7f0da6eae2924255a9cb1f0 on modify-priority into d89abfb3837aa09baa0b8a8d4c40ad54c49b3466 on development.


🍱 Adds TeamSpeak

Added icon for TeamSpeak

Hi, please add a transparent version and an SVG version.

Hi, changed png icon and added svg icon

Hi, please upload an actual SVG instead of a PNG file inside of an SVG.

Yeah, my bad changed the SVG

Yes I did read the new guidelines (I already contributed here)
Could not find a proper SVG so I ended with a black monocrhome one, ugly but thought this would be OK with rules
I finaly found a good SVG icon now
Just commited, let me know if it's OK
Sorry for the difficulties


Fix tests if ~/.aws/shell/ doesn't exist.

Fixes issues with test_keys.py and test_config.py.  Creates the directory that will contain the awsshellrc config file if it doesn't yet exist.  Once it exists, continues with copying the template config file to ~/.aws/shell/awsshellrc.

:shipit:  Looks good, thanks!


fix: extra file path relativity

This makes any extra-files: ['file', '../x'] relative to the package/strategy path, allowing shared files at the root of the manifest to be applied to each package, e.g.
{
  "extra-files": ["gradle.properties"],
  "packages": [
    {"path": "."},
    {"path": "pkg/a"},
    {"path": "pkg/b"}
  ]
}

to result in the following files being updated:
gradle.properties
pkg/a/gradle.properties
pkg/b/gradle.properties

[x] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[x] Ensure the tests and linter pass
[x] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)

Discovered in #1141 🕵♂

Just seen that the tests are failing on Windows. 🙄 I'll try look into it tonight.

Okay, all tests should be passing for Windows again in 12d9f80711b09a5e9d01a0d03aa03efc06c7b3bc.
Also, in the current state (and unchanged in this PR), it is possible for files to be edited outside of the git project folder, e.g. extra-files: ["~/.m2/"]. I assume GitHub Actions are secure, but should this maybe be looked at in a separate issue? Maybe I'm just being too cautious.

Sure, I'll see what I can do to restrict the various path shortcuts like ~, ../../../../, etc.

So /path after this PR is merged will indeed point to the git root. I just need to account for and strip any leading ../, ~/, etc.


Upgrade to 0.11.1

New ghost version 0.11.1 is released. May be, do you have to update your repository?

please, upgrade your repos. to 0.11.2 version.

Hey @23W
Yeah, I've seen the update notes. The repository will be updated shortly as soon as I will have time.
There is no need to open issue for every minor update the same day it was released :)
Meanwhile if you are really in a harry, I've set up this repository (and that was an initial intention) to be easily updated by anyone.
All I do for every update in this repository is running make command in the root on my CentOS machine.
I will close this ticket when this repo will be updated.


Add page service

Codecov Report

Merging #111 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #111   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          20     21    +1
  Lines         699    745   +46
=====================================
+ Hits          699    745   +46

Impacted Files
Coverage Δ

page.go
100% <100%> (ø)

goshopify.go
100% <100%> (ø)
:arrow_up:

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 0e0df9e...50fcdb3. Read the comment docs.


[SQUASH MERGE] Fix GitHub CI failures with the new ubuntu-latest

Sample failures:

https://github.com/mfem/mfem/actions/runs/3590199014
https://github.com/mfem/mfem/actions/runs/3590198827

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

Thanks for the fix, @v-dobrev!
Is the change to MfemCmakeUtilities.cmake fixing this problem?
cc1plus: error: unrecognized argument to ‘-flto=’ option: ‘auto -ffat-lto-objects -flto=auto’

(Just trying to understand what the problem was and how it was fixed)

Yes. The problem was that MPI_CXX_COMPILE_FLAGS is defined as a single string: "-flto=auto -ffat-lto-objects -flto=auto". Adding that with target_compile_options was causing CMake to add it to command lines as a single option quoted in double quotes. The solution was to convert it to a CMake list -- similar to how the same is done in the CMake macro add_mfem_examples.


( SP:  1) Improved security for bookmarks endpoints

[x] Secured getBookmarkedOffers function, so that only the creator of the bookmarks can retrieve them.
[x] Secured toggleOfferBookmark, so that only the creator of the bookmarks can change them.

I was able to get other user's bookmarks, please fix it.

I logged in as<EMAIL_ADDRESS>
 2. Found other user's ID in a database  3. Was able to get other user's bookmarks

thank you for your attention! I updated tokenValidation.js and tests, now everything should work properly.


Add optional feature to set the SO_REUSEADDR option before binding th…

Background
Add an optional parameter to set the SO_REUSEADDR option on the TCP socket before binding
it (default false). Can reduce the amount of "bind: address already in use" errors when doing many
connections with the same address and port combination, like the ones that happened on https://github.com/tsenart/vegeta/issues/583.
Checklist

[x] Git commit messages conform to community standards.
[x] Each Git commit represents meaningful milestones or atomic units of work.
[ ] Changed or added code is covered by appropriate tests.

Hey, thanks for the patch. I have couple question.

Does this work on every OS/architecture pair we ship releases to? If not, that's fine. We just need to document it properly and make sure this only runs on the supported ones. See the latest release for the supported targets: https://github.com/tsenart/vegeta/releases/tag/v12.11.0
Are there any risks / trade-offs involved with setting this on outgoing connections? I've used this when binding to a port to receive incoming requests but never to outgoing connections.

Here's what GPT4 had to say about this: https://chat.openai.com/share/fb6418fa-8beb-468c-8d9c-6299f54ef42a

Yeah, I'm aware of the risks and the follow article explain it really well:
https://hea-www.harvard.edu/~fine/Tech/addrinuse.html
I think the main risk is to have a socket A receiving packets that should be received by socket B, but I think it doesn't matter much for the load test itself (it would matter for the report in the end, but I think we could add a note there).

And this post on stackoverflow talks about the different implementation of the REUSEADDR and REUSEPORT flags on many architectures. In resume the REUSEADDR flag stays the same, while we have some minor variations on the REUSEPORT flag.
https://stackoverflow.com/questions/14388706/how-do-so-reuseaddr-and-so-reuseport-differ

About the suggestions made by GPT4, something we cannot or are not allowed to modify sys net ipv4 parameters. For example, decreasing the tcp_fin_timeout will also affect other services, which may not be desirable.

I need to convince myself that this is safe, and so far I haven't been able to. Maybe you can help me get there. If someone runs into "bind: address already in use" even given the fact that we're using HTTP keep alive underneath and re-using TCP connections, it like means the server is very slow to respond, or the network really faulty, or a mix. In either case, the TCP connection would still be open, and the client reading a response, so re-using the local address seems unsafe?
Or is it only applicable when the underlying TCP connection is in TIME_WAIT state? In any case, I'd like to write some sort of integration test that exercises this and gives us some more confidence.

Exactly. On our use case we were executing a load test to a load balancer composed of 8 front end servers. Those servers queries a route table located on another server and do a proxy_pass to one internal server out of 20. We were trying to find out what happens when the communication to the route table service becomes unresponsible. Because how the retries were implemented a request that took milliseconds to be responded went to up 5 seconds. We wanted to know if the front end servers would crash or also become unresponsible but we started to runs into "bind: address already in use". The setting of the reuse option fixed this on our case. It only allows the reuse of TIME_WAIT sockets when you are binding to different combination of remote IP address and port. So if you have a socket in TIME_WAIT with the combination LOCAL_ADDR_A:PORT_A <=> REMOTE_ADDR_A:PORT_X and try the same combination again it will not allow, but if use a combination with another remote IP address or port like LOCAL_ADDR_A:PORT_A <=> REMOTE_ADDR_B:PORT_X it will reuse the LOCAL_ADDR_A:PORT_A when binding.

If you're hitting "bind: address in use" issues in your load tests, it typically means you're exhausting the capabilities of the network stack on the host. SO_REUSEADDR and SO_REUSEPORT won't meaningfully impact those constraints. And, in any case, it's a situation that you would — should! — never encounter in a normal deployment, so it doesn't make sense to try to accommodate in a vegeta load test.
Instead, you want to make sure that vegeta creates no more than a reasonable number of connections to a given target host. The best way to do that is by setting -max-connections to a value like 8 or 16 or 32. And if that means you can't do as many RPS as you want, then you need to run vegeta on multiple hosts.


Enhancement - Add Owner/Notes Column to Systems

Add a column for Owner and / or a Notes column to the Systems view.  Useful for identifying different systems (srv-acme-132 is a domain controller, srv-acme-042 is an FTP server, etc) and for identifying workstation ownership (lap-acme-143 is Susan's laptop).

Will put that in the next release.


Initial playwright setup - test find flow

Adds a browser test using Playwright that walks through the main user journey for a find user.
This involves:

selecting some filters
select a download file format
clicking download
clicking the link in the email that is received later
downloading the final report on the page

We need to do some incredibly funky stuff around authentication to get a valid user session (in a way that could feasibly work against dev and test environments, too). We (ab)use authenticator's magic links flow to create a link as if we're an assessor of a new "post-award-e2e-tests" fund (which we inject into the local mock data for authenticator in a PR on that repo). When we use the magic link, it sets a cookie on the .levellingup.gov.localhost that is valid for Find, so we become effectively logged in.

At the moment I haven't added this to CI/CD, and it isn't able to run against dev/test environments. These will need to come in future development. But you are able to run the tests on your laptop against your own running services. This should make it possible to develop these tests out as we build the new features/journeys we're planning.

Show the thing
Note: the errors at the start are from the authentication flow, and are "correct" (insofar as they do the auth correctly), but they definitely look weird because we have to jump through some weird rabbit-holes to get an authenticated session.

One question I have is whether these tests belong in this repo and not in Nara's e2e-checks repo?

It's a good question. I have very intentionally put the tests here so that they are co-located with the rest of our code. This should mean that:

developers find it easier to 'stumble' across, and therefore learn about, these browser tests
it's easier for developers to run the tests because it can be done with a pytest command in a repo we mainly use
developers can add features and browser tests for those features in the same PR
it's easier for us to run these tests in CI (eventually) because the tests are just right here


Dragon Curve challenge is solved.

The 1.3.09-Challenge-DrawTheDragonCurve  and 1.3.09-Solution-DrawTheDragonCurve core modules are identical.

Whoops. Good catch. Fixed.


Intermittent failure - Ballerina tools integration tests - ServicePackagingTestCase

Description:
Intermittent failure - ServicePackagingTestCase
Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:

This is fixed now.


feat: 5648 - deep link for Prices (+ OxF fixes)

What

Now Prices is part of detected URLs regarding deep links.
We cannot open directly a specific Prices page on Smoothie because the GoRouter package somehow hides the subdomains.
At least it will open Smoothie.
Minor fixes regarding OxF too.

Fixes bug(s)

Closes: #5648

Impacted files

AndroidManifest.xml: added an entry for Prices regarding deeplinks
launch_url_helper.dart: added beauty, products and petfood regarding deeplinks
Runner.entitlements: added an entry for Prices, beauty, products and petfood regarding deeplinks

Codecov Report
Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 7.00%. Comparing base (4d9c7fc) to head (04be699).
Report is 384 commits behind head on develop.

Files with missing lines
Patch %
Lines

...ages/smooth_app/lib/helpers/launch_url_helper.dart
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           develop   #5734      +/-   ##
==========================================
- Coverage     9.54%   7.00%   -2.55%
==========================================
  Files          325     406      +81
  Lines        16411   21655    +5244
==========================================
- Hits          1567    1516      -51
- Misses       14844   20139    +5295

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

@monsieurtanuki I was wrong about the domain.
GoRouter knows it with GoRouterState.uri

@monsieurtanuki I was wrong about the domain. GoRouter knows it with GoRouterState.uri

Good news!


Some tracking URL parameters

@FadeMind commented on Sat May 11 2019
Please add to default list
ad_sub
pbw
Sample NSFW URL:
https://www.pornhat.com/video/6280/club-cougar-joins-the-party/?ad_sub=321
https://www.xozilla.com/videos/146738/amoral-czech-sluts-group-sex-party/?pbw=1
They are taken from https://www.gonzoxxxmovies.com/category/party TUBE after click on some  videos links.

Information
Value

Operating system:
Windows 10 1809 x64

Browser:
Google Chrome Stable x64 (lastest)

AdGuard version:
7.0.x Nightly

Stealth Mode:
enabled

I back to Adguard after some time (and so far no more BSOD... 😁 )

@FadeMind commented on Sat May 11 2019
On polish portal interia.pl they using # and & marks instead of ? in URL backend tracking:
https://www.interia.pl/#utm_source=Fakty&utm_medium=logo&utm_campaign=powrot_z_wew&iwa_source=logo

@FadeMind in order to add new parameters to the default list we need to know what exact ad network supports it and how widespread it is. We cannot add every parameter name there.


Deprecated extension documentation link is broken

The deprecation warning emitted when a deprecated feature is used contains a documentation link that is 404.
[2020-05-06 00:14:08.017][1][warning][misc] [bazel-out/k8-opt/bin/source/extensions/common/_virtual_includes/utility_lib/extensions/common/utility.h:65] Using deprecated extension name 'envoy.grpc_web' for 'envoy.filters.http.grpc_web'. This name will be removed from Envoy soon. Please see https://www.envoyproxy.io/docs/envoy/latest/intro/deprecated for details.

The link https://www.envoyproxy.io/docs/envoy/latest/intro/deprecated returns 404
$ curl -L -v https://www.envoyproxy.io/docs/envoy/latest/intro/deprecated
*   Trying <IP_ADDRESS>:443...
* Connected to www.envoyproxy.io (<IP_ADDRESS>) port 443 (#0)
* ALPN, offering http/1.1
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
* Server certificate: envoyproxy.io
* Server certificate: Let's Encrypt Authority X3
* Server certificate: DST Root CA X3
> GET /docs/envoy/latest/intro/deprecated HTTP/1.1
> Host: www.envoyproxy.io
> User-Agent: curl/7.70.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 404 Not Found
...

Whoops, I think that's due to the generally awesome docs refactor in #10730
We could point folks to https://www.envoyproxy.io/docs/envoy/latest/version_history/version_history instead, but making them wander through pages doesn't seem as useful.  Per Matt's point over in #11058 I wonder if we can leverage the annotations to print out something field-specific and useful, or just point them at API docs which will be specific and useful?
@ggreenway @mattklein123 @htuch

In this specific case, this is just the new vs. old names for extensions, so we can provide a fixed anchor.
It should be fairly easy to autogenerate a link back to the field specific docs in general though, from browser copy+paste, this is what the href looks like: https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/core/v3/health_check.proto#envoy-v3-api-field-config-core-v3-healthcheck-transport-socket-match-criteria

Ideally, we'd have a released version not point at latest, but at it's version of the docs, so any future movement of pages won't invalidate those links.
Field-specific doc-links would be great, but I don't know if it's worth the effort or not.

Ideally, we'd have a released version not point at latest, but at it's version of the docs, so any future movement of pages won't invalidate those links.

Yeah this would probably be the "simplest." I wonder if it could be done with a short generated header/cc file that is based on the VERSION file?

We already have this constant that we use for the build version string.

Independently of how this link will be managed in the future, shipping envoy versions are emitting this message today. Is it possible to add a redirect to support people who are currently seeing this message?

xref #8465

Is it possible to add a redirect to support people who are currently seeing this message?

Doc PRs appreciated.

I'll fix this soon. My mess, mine to cleanup :)


Javascript Language Server : Increase File Limit

We have a repo with ~10k js files. Continously getting the configure excludes message. Need a way to increase the number of files that vscode server can process.
A workaround also coud be:
Our repo contains both frontend and backend code, so maybe we can configure excludes based on the current open file ... Process only front end files if current open file is in front end folder :thinking:

Our repo contains both frontend and backend code

@yj7 Is your code split up into projects either using a jsconfig / tsconfig?


glusterfs mount on coreos using special docker container - problem with monitoring in kubernetes

Hi, I'm not sure whether this is the right place to post the problem, but the main problem is kubernetes running specifically on coreos, so I'll give it a try.
I was able to mount a glusterfs filesystem into coreos using this guide: https://huaminchen.wordpress.com/2015/06/09/share-hosts-mount-namespace-with-docker-containers/ with some modifications - I needed to use shared volume mounts with docker.
To be able to run the whole thing, I needed to change the MountFlags parameter in the systemd config of docker.service to 'shared'
MountFlags=shared

Then I was able to run this docker image to be able to mount the glusterfs from within the docker container:
docker run --privileged --net=host  -v /:/host:shared -i -t centos bash

From within the container I just installed the glusterfs tools and mounted the glusterfs volume onto a directory from the /host path, so it would be usable from within the VM.
That actually worked, but with 2 drawbacks:

I'm not able to stop the container, even after manually unmounting the glusterfs volume from within the container, the process just hangs. To be able to clearly unmount, I need to stop kubelet and docker in coreos and restart the vhole VM (btw dockker stops at least a minute this way).. this is a problem but I can somehow live with it

I am able to use the mount point in kubernetes pods using hostpath volumes, BUT: there is a problem with getting monitoring data from the kubernetes heapster pod into the influxdb-grafana pod (no idea why, I use the standard config from kubernetes repo) - node data is being collected from every node, but there is no new data from the running pods - it's not being written, even the pod names of the newly created pods are missing... I think there is also a problem with writting logs into the ES-Kibana pods (also standard setup from the kube repo), but at first I need to solve the monitoring.

This happens when I run the mounter docker on coreos start slightly before the kubelet process starts. I realized, that when I run the mounter docker after kubelet process starts and after some basic kubernetes containers are online - in this cas the monitoring data of the pods is being logged from heapster into influxdb. I suppose there is some magic being done with the mounts after kubelet starts, but I have no idea what that is and what to do about, and I also have no idea how to run the mounter docker after kubelet, but after all the mounting magic happens (I was also able to run the mounter right after kubelet started, using systemd ExecAfter, but it still was too soon for some reason...)
Could anybody help me understand what's under the hood or maybe suggest a solution of the problem? Maybe there's a cleaner way to mount glusterfs on coreos, but I haven't found any. Is there? This solution works almost perfectly, but still just 95% good... I just realized that after a week of usage, everything worked like a charm, except monitoring of the pods and some logging.
I'm using the current stable version of coreos - 1222.2.0, and kubernetes 1.3.5 (v1.3.5+coreos.0)

So, if someone would be interested, I 'fixed' this with a temporary workaround, I created a systemd glusterfs-fix.service with this definition:
[Unit]
Description=glusterfs-fix
After=docker.service kubelet.service
Requires=docker.service kubelet.service

[Service]
User=core
TimeoutStartSec=0
ExecStartPre=-/usr/bin/docker rm glusterfs-fix
ExecStartPre=/usr/bin/docker pull  pixelfederation/coreos-glusterfs-client:1.0
ExecStart=/home/core/bin/glusterfs-fix
ExecStop=/usr/bin/docker stop glusterfs-fix

[Install]
WantedBy=multi-user.target

while these are the contents of the /home/core/bin/glusterfs-fix file:
#!/bin/bash

while [[ $(docker ps | wc -l) == "1" ]]; do sleep 1; done && /usr/bin/docker run --name glusterfs-fix --privileged --net=host -v /:/host:shared pixelfederation/coreos-glusterfs-client:1.0

Hi Martin,
Out of curiosity,  is there a specific reason to propagate a mount from the
host down to the container instead of using the Kubernetes glusterfs plugin
for that POD ?    As documented here:
http://kubernetes.io/docs/user-guide/volumes/#glusterfs
regards,
Jfn
On Fri, Sep 30, 2016 at 4:20 AM, Martin Fris<EMAIL_ADDRESS>wrote:

So, if someone would be interested, I 'fixed' this with a temporary
workaround, I created a systemd glusterfs-fix.service with this definition:
[Unit]
Description=glusterfs-fix
After=docker.service kubelet.service
Requires=docker.service kubelet.service
[Service]
User=core
TimeoutStartSec=0
ExecStartPre=-/usr/bin/docker rm glusterfs-fix
ExecStartPre=/usr/bin/docker pull  pixelfederation/coreos-glusterfs-client:1.0
ExecStart=/home/core/bin/glusterfs-fix
ExecStop=/usr/bin/docker stop glusterfs-fix
[Install]
WantedBy=multi-user.target
while these are the contents of the /home/core/bin/glusterfs-fix file:
#!/bin/bash
while [[ $(docker ps | wc -l) == "1" ]]; do sleep 1; done && /usr/bin/docker run --name glusterfs-fix --privileged --net=host -v /:/host:shared pixelfederation/coreos-glusterfs-client:1.0
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/coreos/coreos-kubernetes/issues/696#issuecomment-250687352,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOflqIEbPSiNCLwUwz4RNyvJS3RUoAIbks5qvMY_gaJpZM4KJWHn
.

@somejfn well, the reason is obvious I suppose (or I didn't understand something) - regarding this guide: https://github.com/kubernetes/kubernetes/tree/master/examples/volumes/glusterfs I need to have glusterfs client installed on the kubernetes nodes.

The example assumes that you have already set up a Glusterfs server cluster and the Glusterfs client package is installed on all Kubernetes nodes.

But I don't know how to install glusterfs client on the coreos nodes (on which kubernetes is running). Did I not understand anything from the guide or is there a way to install glusterfs client on coreos and I didn't find it?

Normally the kubelet performs the mount action for the POD you want the
volume allocated so you don't have to mount the FS on all the Kubernetes
hosts your POD could potentially end running. I used the nfs plugins that
way and since the NFS client is built into the kernel there is no need for
a client to be installed in coreos.
I don't know specifically about gluster,  but it may be a case where the
kubelet need some client bin/libs to perform the mount action and doesn't
find it on coreos.   In this case the mount would fail and you'd find the
error in the kubelet logs.
On Fri, Sep 30, 2016 at 7:56 AM, Martin Fris<EMAIL_ADDRESS>wrote:

@somejfn https://github.com/somejfn well, the reason is obvious I
suppose (or I didn't understand something) - regarding this guide:
https://github.com/kubernetes/kubernetes/tree/master/
examples/volumes/glusterfs I need to have glusterfs client installed on
the kubernetes nodes.
The example assumes that you have already set up a Glusterfs server
cluster and the Glusterfs client package is installed on all Kubernetes
nodes.
But I don't know how to install glusterfs client on the coreos nodes (on
which kubernetes is running). Did I not understand anything from the guide
or is there a way to install glusterfs client on coreos and I didn't find
it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/coreos/coreos-kubernetes/issues/696#issuecomment-250726592,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOflqFLjldIWVqdzsrMH-aWhc6q_Fxnxks5qvPj5gaJpZM4KJWHn
.

yes, that's exactly the problem, kubelet doesn't find glusterfs client libs, because they aren't there. I don't want to use nfs because it's slow and it is not scalable comparing to glusterfs.
So the only workaround hack I was able to find was this - run a docker container with glusterfs client with a volume mounted in shared mode (docker volume flag). The docker container mounts the glusterfs filesystem into the shared volume, which is accessible from the host VM. Then I'm using HostPath volumes in Kubernetes, which point to the shared mount point ... It's an ugly hack, but it works and is way faster comparing to nfs.

I remember a similar problem with Ceph and a solution was to use a
container to alias the rbdmap command.  So the kubelet was able to find
"rbdmap" and mount the volume for the POD.  Maybe the same could work for
Gluster and avoid the hostPath hack.
On Fri, Sep 30, 2016 at 10:13 AM, Martin Fris<EMAIL_ADDRESS>wrote:

yes, that's exactly the problem, kubelet doesn't find glusterfs client
libs, because they aren't there. I don't want to use nfs because it's slow
and it is not scalable comparing to glusterfs.
So the only workaround hack I was able to find was this - run a docker
container with glusterfs client with a volume mounted in shared mode
(docker volume flag). The docker container mounts the glusterfs filesystem
into the shared volume, which is accessible from the host VM. Then I'm
using HostPath volumes in Kubernetes, which point to the shared mount point
... It's an ugly hack, but it works and is way faster comparing to nfs.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/coreos/coreos-kubernetes/issues/696#issuecomment-250754793,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOflqGK3kqLn2wUn-we2g54dTSziqhSEks5qvRj7gaJpZM4KJWHn
.

yes, I was also considering this idea, but I haven't found any information regarding how to do it ... or it more complicated than the hostpath solution... could you show me an example of the rbdmap command aliasing? I could try to reproduce it with glusterfs

Was:
cat /opt/bin/rbd
#!/bin/sh
exec docker run -v /etc/ceph:/etc/ceph ceph/rbd $@
On Fri, Sep 30, 2016 at 10:23 AM, Martin Fris<EMAIL_ADDRESS>wrote:

yes, I was also considering this idea, but I haven't found any information
regarding how to do it ... or it more complicated than the hostpath
solution... could you show me an example of the rbdmap command aliasing? I
could try to reproduce it with glusterfs
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/coreos/coreos-kubernetes/issues/696#issuecomment-250757368,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOflqPfzDbCRTsoUa1msKWCmh9fi2ZQwks5qvRtfgaJpZM4KJWHn
.

I can't quite see how kubelet is able to access the ceph ... does this alias create a mount on the host? I suppose not... So is the ceph connection created in the docker context which is then somehow accessible to kubelet through k8s docker containers?
This looks like magic to me :)

Newer 1.4.x hyperkube images should have all of the required client tools to mount storage for you: https://github.com/coreos/coreos-kubernetes/blob/3f25cfebc929c62ab41bc7af6ad8d1e6fad7c283/Documentation/kubelet-wrapper.md#allow-pods-to-use-rbd-volumes

So I don't need to install anything and just create a glusterfs persistent volume in kubernetes and the volume will be created? That would help quite a lot... or do you only mean rbd/ceph?

@Rastusik did this work for you by just creating the PV for Gluster on kubernetes 1.4.x?

@pcm32 no it didn't ... I'm getting this error:
MountVolume.SetUp failed for volume "kubernetes.io/glusterfs/acbe81ea-8fbf-11e6-8d12-fa163e5ec993-gluster-pv" (spec.Name: "gluster-pv") pod "acbe81ea-8fbf-11e6-8d12-fa163e5ec993" (UID: "acbe81ea-8fbf-11e6-8d12-fa163e5ec993") with: glusterfs: mount failed: mount failed: exit status 32
Mounting arguments: <IP_ADDRESS>:kube_vol1 /var/lib/kubelet/pods/acbe81ea-8fbf-11e6-8d12-fa163e5ec993/volumes/kubernetes.io~glusterfs/gluster-pv glusterfs [log-level=ERROR log-file=/var/lib/kubelet/plugins/kubernetes.io/glusterfs/gluster-pv/test-2703916870-ru9e0-glusterfs.log]
Output: mount: unknown filesystem type 'glusterfs'

I think @robszumski meant that kubelet is now able to mount RBD and iSCSI volumes, not glusterfs volumes

@pcm32 thanks!

Going to close this as I believe the underlying issue has been resolved (glusterfs tools are included in quay.io/coreos/hyperkube:v1.4.3+coreos.0 and newer. See https://github.com/coreos/kubernetes/releases for all hyperkube releases.
If this needs to be re-opened please let me know


Fix Embargo

This PR is an attempt to fix all issues relating to embargoed Dandisets.
I've been able to isolate the embargoed Dandiset issue to the fact that requesting dandisets/?user=me does not appear to return Dandisets that are embargoed. I'll start scouring the docs for an alternative request.
Once this is complete, we can move on to #814.

A simple fix. Turns out this request turns everything except embargoed Dandisets by default. Need to add another search query (e.g. dandisets/?user=me&embargoed=true) to the end of it.

@CodyCBakerPhD Aside from the NIH Award Number stuff, can you confirm this is behaving as expected?

When I try to create one one on staging I get this error
dandi.es.js:199 Uncaught (in promise) Error: API is not authorized. Please provide a valid token.
    at K.authorize (dandi.es.js:199:15)
    at async K.init (dandi.es.js:182:7)
    at async Button.onClick [as __onClick] (UploadsPage.js:122:17)

But it's definitely the right credentials for staging

I also can't see any of my embargoed Dandisets on the loose selector when my API keys are set

Sorry! Try again

OK I can now see them in the selector
One thing, not sure if you want to deal with it in this PR or a follow-up : the NIH grant number validation did not occur until I hit 'Submit' (I clicked off it and waited to see if that would trigger but it did not) and then it popped up very briefly but submission of the modal finished (would have expected the modal to stay open if there was an error) before I could fix it
However, the dandiset did get created and seems fine. Maybe it would have problems at some level without the right kind of grant ID format, but the basic feature did work

Let's handle the NIH grant number stuff before merging this PR, as this will enable embargo again. I'll start this in a linked follow-up.

Alright invalid NIH grant numbers are properly blocked now! I'm going to skip the auto-parsing of the non-delimited string copied off NIH Reporter because DANDI itself does not accept this format directly.

Cool
CI tests failing now - you wanted to work on NIH number formatting on a separate branch/PR that gets merged into this one before merging either to main?

Blocking Dandiset creation when the user provides an invalid NIH grant number has been implemented here. I'm actually going to skip the number formatting since DANDI does not allow this. Would it be correct here to assume we want to maintain parity between ourselves and DANDI?

I think it's probably fine at this point, the other idea was a 'nicety'
As per meeting; we can merge this whenever you're ready but I won't cut a new release until after user days

Sounds good to me. Will need your review here


#744: Fix MAVEN_ARGS by separating arguments

Fixes: #744
This quick bug fixes the MAVEN_ARGS variable. The reason for the bug was a missing whitespace that separates the arguments.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

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

Totals

Change from base Build<PHONE_NUMBER>9:
0.0%

Covered Lines:
6311

Relevant Lines:
9085

💛  - Coveralls


Update SpyMemcached dependency to latest version - 2.11.1

Scheduled for next release - 1.7.0

is there any update on this?

following up on this, as Scala has reached a mature 2.11.4 status

Sorry guys for waiting - GitHub for some reason stopped sending me notifications on issues opened, I will update it as soon as possible - meaning sometimes this week.

:+1:
Great lib just bumping

The latest 1.7.1 release of Shade uses SpyMemcached 2.11.7, so this can now be closed as well


NewtonsoftJsonOutputFormatter fails on sync flushes

https://github.com/aspnet/AspNetCore/issues/7644#issuecomment-470690541
System.InvalidOperationException: Synchronous operations are disallowed. Call WriteAsync or set AllowSynchronousIO to true instead.

at Microsoft.AspNetCore.Server.IIS.Core.HttpResponseStream.Write(Byte[] buffer, Int32 offset, Int32 count)

at Microsoft.AspNetCore.Server.IIS.Core.WrappingStream.Write(Byte[] buffer, Int32 offset, Int32 count)

at Microsoft.AspNetCore.WebUtilities.HttpResponseStreamWriter.FlushInternal(Boolean flushEncoder)

at Microsoft.AspNetCore.WebUtilities.HttpResponseStreamWriter.Write(String value)

at Newtonsoft.Json.JsonTextWriter.WriteValue(Guid value)

at Newtonsoft.Json.JsonWriter.WriteValue(Nullable`1 value)

at Newtonsoft.Json.JsonWriter.WriteValue(JsonWriter writer, PrimitiveTypeCode typeCode, Object value)

at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeObject(JsonWriter writer, Object value, JsonObjectContract contract, JsonProperty member, JsonContainerContract collectionContract, JsonProperty containerProperty)

at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeList(JsonWriter writer, IEnumerable values, JsonArrayContract contract, JsonProperty member, JsonContainerContract collectionContract, JsonProperty containerProperty)

at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.Serialize(JsonWriter jsonWriter, Object value, Type objectType)

at Newtonsoft.Json.JsonSerializer.SerializeInternal(JsonWriter jsonWriter, Object value, Type objectType)

at Newtonsoft.Json.JsonSerializer.Serialize(JsonWriter jsonWriter, Object value)

at Microsoft.AspNetCore.Mvc.Formatters.NewtonsoftJsonOutputFormatter.WriteResponseBodyAsync(OutputFormatterWriteContext context, Encoding selectedEncoding)

at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeResultAsync(IActionResult result)

at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeNextResultFilterAsync[TFilter,TFilterAsync]()

at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResultExecutedContext context)

at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.ResultNext[TFilter,TFilterAsync](State& next, Scope& scope, Object& state, Boolean& isCompleted)

at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeResultFilters()
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeNextResourceFilter()

at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContext context)

at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)

at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeFilterPipelineAsync()

at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeAsync()

at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)

at Microsoft.AspNetCore.Routing.EndpointRoutingMiddleware.Invoke(HttpContext httpContext)
   at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context)

at Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.MigrationsEndPointMiddleware.Invoke(HttpContext context)

at Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.DatabaseErrorPageMiddleware.Invoke(HttpContext httpContext)

at Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.DatabaseErrorPageMiddleware.Invoke(HttpContext httpContext)

at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)

Thanks, would it be helpful to share my startup.cs?

In the AsyncIO PR I added temporary overrides for XML and razor, but Json didn't get one for some reason. The tests passed without it, likely because they never wrote large enough data to fill the buffer and trigger as sync flush.
@GusBeare how large is the object you're serializing? Does this repro with small responses?
Workarounds are already outlined in https://github.com/aspnet/AspNetCore/issues/7644.

Not huge, about 600 rows.

Not small. Those buffers are only KB. Go ahead and apply the workaround. We'll get this fixed for the next preview. @mkArtakMSFT

Many thanks.  I'll try the workarounds tomorrow: getting late here. Had enough.

Though it would be helpful if you could point me in the right direction as to how to do this globally.
There are lots of failing requests.
"Each server has a AllowSynchronousIO option that controls this behavior and the default for all of them is now false."
I can't find anything on how to set it for IIS in process.
I am still baffled as to why it's failing though because these are async requests from angularjs.

The JSON serializer is synchronously writing to the response body.
For IIS In-proc it should be something like this.
https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-2.2#iis-options
// Startup.ConfigureServices
services.Configure<IISServerOptions>(options =>
{
  options.AllowSynchronousIO = true;
});

Confirming this is an issue on GetJsonAsync from a database when the rows count (in our case) exceeds 3 rows. We have added the suggested fix "options.AllowSynchronousIO = true;" but does not fix the issue.

I have this same issue using Kestrel .net core 3. Even with the following code implemented:
{
  options.AllowSynchronousIO = true;
});

Is there a Kestrel part to this workaround? I am not using IIS, just Kestrel.

Our solution was to replace GetJsonAsync with straight GetAsync and deserialise the stringcontent for the time being while the issue is sorted out - this has no issues with the record load.

@aford22 what was the line before that? The complete sample for Kestrel should be:
services.Configure<KestrelServerOptions>(options =>
{
  options.AllowSynchronousIO = true;
});

Bingo, @Tratcher ! That worked perfectly.
Thank you.

I know this is closed, but I just discovered why I was suffering from this issue on very small requests (100 bytes).  I had a circular reference between a two classes in EF Core, which began generating a larger response and triggering this issue.  Although setting AllowSynchronousIO = true in the method, for me, did not resolve the issue.

I still have this error in preview 5, I'm not sure how it got here. The above mentioned workaround worked for me though.
I thought it was worth mentioning since it was supposed to be fixed in preview 4.

@kevinsnijder this PR was only a temporary fix. https://github.com/aspnet/AspNetCore/issues/6397 replaced it and was part of preview5. If you're having a similar problem with preview5 please open a new issue and tell @pranavkm.

@Tratcher I looked at some of the referenced issues and I was unable to determine if Json.net will still throw if I turn this on in preview 8. I'm assuming so as it does sync operations (unless there was a pr that I'm not seeing).

@pranavkm were you able to determine if this is still an issue?

@niemyjski could you please file a separate issue with a clear description of what you're seeing?


Fix ResourceQuotaDetails quotas display bugs

Signed-off-by: Sebastian Malton<EMAIL_ADDRESS>fixes https://github.com/lensapp/lens/issues/5892

Nice, it actually works now. But, perhaps unrelated, is this right?

cpu is 500m / 1k? Isn't that 0.05% not 50%? Used the Resource Quotas example from https://kubernetes.io/docs/concepts/policy/resource-quotas/#:~:text=apiVersion%3A v1,"low"] (the above png shows the pods-high resource quota, which has hard.cpu = "1000"

I have now also fixed what @jim-docker found,
here is a screenshot:


Update lightfm_utils.py

LightFm model predict method expect user_ids type of int or np.int32 data type. Made small change on prepare_all_predictions.
Description

Related Issues

Checklist:

[x] I have followed the contribution guidelines and code style for this project.
[x] I have added tests covering my contributions.
[ ] I have updated the documentation accordingly.
[x] This PR is being made to staging branch and not to main branch.

Codecov Report

Merging #1624 (b37a577) into staging (d005c1a) will increase coverage by 57.00%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##           staging    #1624       +/-   ##
============================================
+ Coverage     0.00%   57.00%   +57.00%
============================================
  Files           88       88
  Lines         8956     8956
============================================
+ Hits             0     5105     +5105
- Misses           0     3851     +3851

Flag
Coverage Δ

nightly
?

pr-gate
57.00% <100.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

recommenders/models/lightfm/lightfm_utils.py
62.50% <ø> (+62.50%)
:arrow_up:

recommenders/models/rbm/rbm.py
83.60% <100.00%> (+83.60%)
:arrow_up:

recommenders/datasets/mind.py
0.00% <0.00%> (ø)

recommenders/datasets/movielens.py
69.46% <0.00%> (+69.46%)
:arrow_up:

recommenders/models/sasrec/model.py
26.28% <0.00%> (+26.28%)
:arrow_up:

recommenders/models/sasrec/sampler.py
89.58% <0.00%> (+89.58%)
:arrow_up:

recommenders/datasets/download_utils.py
90.00% <0.00%> (+90.00%)
:arrow_up:

recommenders/models/newsrec/models/npa.py
95.58% <0.00%> (+95.58%)
:arrow_up:

recommenders/models/newsrec/models/naml.py
92.43% <0.00%> (+92.43%)
:arrow_up:

recommenders/models/newsrec/models/nrms.py
91.37% <0.00%> (+91.37%)
:arrow_up:

... and 13 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 9898ec6...b37a577. Read the comment docs.


Adding metrics webtop and hud site ids as configuration

This change will add the hud and webtop site ids

:+1:

:alien::+1:


Bump remix run deps to 1.16.0

This bumps all remix-run deps to 1.16.0

One thing 1.16 adds is the new experimental dev server.  I'm keen to explore this later on.
Thanks for doing this.


📄  Add MIT Licence to the project (friendly contribution)

Motivation
After taking a look at your repository, I was, first of all, very proud of your constant contributions, great ideas and above everything: ambition!
I wanted to contribute to tell you that I'm very proud of you and I'm always watching you grow, learn and become better 💪
Med Redha

Good evening,
I am pleased to hear that especially from you,
It has been a long time though, I thought you forgot us at all.
I have sent you an invitation on hangout, and to your email but you have never replied.
Anyway take care my friend, and of course I will continue take your note in consideration.
Good luck
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Med Redha @.>
Sent: Wednesday, July 14, 2021 11:11:46 PM
To: kanounfoued/word-researcher @.>
Cc: Subscribed @.***>
Subject: [kanounfoued/word-researcher] 📄 Add MIT Licence to the project (friendly contribution) (#42)
Motivation
After taking a look at your repository, I was, first of all, very proud of your constant contributions, great ideas and above everything: ambition!
I wanted to contribute to tell you that I'm very proud of you and I'm always watching you grow, learn and become better 💪
Med Redha

You can view, comment on, or merge this pull request online at:
https://github.com/kanounfoued/word-researcher/pull/42
Commit Summary

📄 add MIT Licence to the project (friendly contribution)

File Changes

A LICENSE.txthttps://github.com/kanounfoued/word-researcher/pull/42/files#diff-d0ed4cc3fb70489fe51c7e0ac180cba2a7472124f9f9e9ae67b01a37fbd580b7 (21)

Patch Links:

https://github.com/kanounfoued/word-researcher/pull/42.patch
https://github.com/kanounfoued/word-researcher/pull/42.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/kanounfoued/word-researcher/pull/42, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHR4SPSSLGMGMBV44KPBDVLTXYDSFANCNFSM5AMKHLOQ.


Box Manipulation interactives don't load properly

The interactives use a library -three- for graphics rendering.
three functions attempt to load images from the server, but are denied - see below.
I cannot work on this as I don't have any access to the server
Resources that could help:
https://stackoverflow.com/questions/40099566/three-textureloader-load-image-fail-no-access-control-allow-origin-header-is
https://discourse.threejs.org/t/textureloader-with-external-image-link-cors/2343

I have resolved this issue by configuring the CORS configuration on the cs-field-guide-dev bucket. The origins we now allow are:
https://cs-field-guide-dev.appspot.com and http://csfieldguide.org.nz/


Restore Mirage build in CI after upstream fixes

During #337 we discovered that many of the dependencies of dream-mirage are still being updated to mirage-crypto 1.0.0. This is fine, but it eventually prevented us from getting the Mirage build working again within a reasonable amount of time. This issue is a reminder to try it again once https://github.com/robur-coop/ocaml-letsencrypt/pull/34 is released, and any other dependencies that are still waiting that we may discover subsequently.

You'll need to wait for a release of the mirage tool -- with https://github.com/mirage/mirage/pull/1559 being merged. I will ping you here once I think this should be a smooth sail. :)

Great, thank you!

@hannesm I see the tool has been released with that PR. Is this ready for attention again?

Oh yes indeed. Sorry I forgot to notify you. With the latest mirage you should be able to get dream-mirage and its examples working :)
If you need help with that, let me know and I'll try to find some time to look into that.


[Bug] [RubySrc2Cpg] - IdentifierToCallPass is breaking

Describe the bug
The pass IdentifierToCallPass introduced in the PR, is breaking on the repo - https://github.com/pay-rails/pay.git
To Reproduce
Steps to reproduce the behavior:
1.Scan the repo using the deprecated Ruby frontend
Expected behavior
The repo should get scanned and the pass IdentifierToCallPass should also pass successfully
Looks like when we are doing an instant replacement, we assume that the to-be-deleted (identifier) nodes will never be encountered when we traverse further referencing Identifier nodes. This is not true, and overlapping may occur for identifier nodes connected via  CFG/PostDominate related Edges

I was able to reproduce the issue on master by invoking importCode.rubyDeprecated("/path/to/code").

The stack trace seems to indicate that we are referring to a node that cannot be found, and this seems to be a result of convertToCall as commenting out the body of that method makes the import succeed.

When removing all removeNode/removeEdge operations in convertToCall, the import succeeds, so, my guess is that we are asking for something to be removed that does not exist.

It seems that we are attempting to remove the same nodes/edges multiple times. I was able to confirm that at least for the LOCAL nodes, for which I now have a patch.

Resolved by https://github.com/joernio/joern/pull/4021


how to change the column offset and the row offset

Please ask your question
I can't find the macro definition like"#define column offset"
Additional context
No response

The original functionality of the chip may not have the functionality you mentioned, but we can achieve it through other configuration ways. Please describe the problem you encountered in detail , which will help us better understand your needs and come up with better solutions.


not_landed: add a needinfo to the assignee or the main attacher

When there are r+ patches and no activity in the bug for 2 weeks, we'll needinfo the assignee (if one) or the main patch attacher with a message like this:
There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:foobar, could you have a look please?

How many ni would it do right now?
Le jeu. 21 mars 2019 à 12:19, calixteman<EMAIL_ADDRESS>a
écrit :

@calixteman https://github.com/calixteman requested your review on: #467
https://github.com/mozilla/relman-auto-nag/pull/467 not_landed: add a
needinfo to the assignee or the main attacher.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/mozilla/relman-auto-nag/pull/467#event-2219404776,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAswjhJ1I5VA2sUVybd8FSzZ9W_YP8p0ks5vY2q_gaJpZM4cBNht
.

154
You can check the concerned bugs in the mail: Open bugs with no activity for 2 weeks and a r+ patch which hasn't landed for the 2019-03-20
I just removed few of them like:
https://bugzilla.mozilla.org/show_bug.cgi?id=1529516
because they've status == 'Changes Planned' (it's a patch status from phab)

By the way, I limited to bugs created less than 2 years ago.

Coverage decreased (-0.4%) to 28.02% when pulling 6b02cdf869ee29f282484524c6289bfda48bb304 on calixteman:autofix_not_landed into b6cc55c66b710c8d681a0bdde8fc2097c6273f2f on mozilla:master.


Type inference for generator yield statement

TypeScript Version:  2.2.1
I've just started with Typescript and ES6/ES7 features and have run into the following case where I'm unable to enforce type-safety with generators.
I'm using generators in a context where the return value of the yield statement (the injected value from generator.next(injected)) has a known type interface. I've managed to enforce this contract by extending IterableIterator:
interface TypedIterableIterator<T, N> extends IterableIterator<T> {
    next(value?: N): IteratorResult<T>;
}

However, Typescript is still unable to narrow down the type of injectedNum.
function* yieldNumber(num: number): TypedIterableIterator<number, number> {
    let injectedNum = yield num; // has inferred type `any`
}

function test() {
    let numYielder = yieldNumber(2);
    numYielder.next('give me type-safety'); // successfully fails to compile
}

The only workaround I've found so far is to manually annotate the injected value and cross my fingers that I didn't use the wrong type.
{
    let injectedNum: number = yield num;
    // type-safe from here on... almost
}

This is a very simple use case, but my actual use case is with redux-saga, which heavily uses generators. Example code:
let returnValue = yield call(callback); // return value type of `callback` is lost

@ssynix this comment and this answer, both from #2983 may interest you. You might also want to check out the discussion in #2873.

Thanks for the links! I like the term "generator return type propagation". Couldn't figure out the right set of keywords to look up this topic earlier.
I'm going to close this since it's clearly a duplicate of what's being discussed in mentioned links.


Why only use focal and triplet loss in AlignPS branch

Hi, thanks for your awesome work.
I noticed that the focal and triplet loss are only used in AlignPS branch, not used in RoI-Align branch. And I don't really understand this setting.
But I have a explanation. The reason is positive samples in AlignPS branch (FCOS center 3x3 area) is much more than them in RoI-Align branch (positive proposals). So in AlignPS branch, for focal loss, features from neighbor location is similar and contain many easy samples. For triplet loss, it is much easier to build triplets with more samples.
Looking forward to your reply. Thanks in advance!

Thanks for this great point. Actually, the focal and triplet loss inherit from our conference paper "Anchor-free person search". While in our extension, we add the RoI-Align branch, which shares similar spirits with the traditional two-stage frameworks, e.g., OIM and SeqNet. To make a fair comparison, we only didn't use focal and triplet. I think it may also work to add them.

I see. Thanks for your reply!


spi_nor Erase operation selection is excessively conservative

Summary: SPI_NOR driver is selecting a smaller erase operation in in many situations it doesn't need to
SPI NOR FLASH devices often have multiple erase sizes. 4k, 32k and 64k are very typical.
When spi_nor_erase (link) is invoked part of the loop attempts to pick the largest erase operation for the current address and remaining size (link)
I was erasing parts of a 512MiB NOR device today and observed extremely slow erase speeds. I found that many of the erase operation where using only the 4kiB erase even when the address/remainder was suitable for a much larger operation.
I extracted the main parts of the op selector in order to confirm my suspicions. This can be seen here
erasing 0x40000 bytes starting at 0x4000
loc: 0x4000, remaining: 0x40000, chosen: 0x1000
loc: 0x5000, remaining: 0x3F000, chosen: 0x1000
loc: 0x6000, remaining: 0x3E000, chosen: 0x1000
loc: 0x7000, remaining: 0x3D000, chosen: 0x1000
loc: 0x8000, remaining: 0x3C000, chosen: 0x1000 // should have been a 32k erase
loc: 0x9000, remaining: 0x3B000, chosen: 0x1000
loc: 0xA000, remaining: 0x3A000, chosen: 0x1000
loc: 0xB000, remaining: 0x39000, chosen: 0x1000
loc: 0xC000, remaining: 0x38000, chosen: 0x1000
loc: 0xD000, remaining: 0x37000, chosen: 0x1000
loc: 0xE000, remaining: 0x36000, chosen: 0x1000
loc: 0xF000, remaining: 0x35000, chosen: 0x1000
loc: 0x10000, remaining: 0x34000, chosen: 0x1000 // should have been a 64k erase
loc: 0x11000, remaining: 0x33000, chosen: 0x1000
...

What I would expect to see is that 4k erases are used until 32k is reached, a 32k erase to get to 64k then 64k erases until the last 16 kB. What actually happens is that only 4k erases are used.
The problem is this line. For a larger erase op to be chosen, the final end address must be aligned with that op size. In my example above, the end is only 16kB aligned so this never occurs
The correct check would be size >= (1 << etp->exp) (updated example. Change is to line 30). This results in the desired/expected output with the largest applicable erase op being used at each step
erasing 0x40000 bytes starting at 0x4000
loc: 0x4000, remaining: 0x40000, chosen: 0x1000
loc: 0x5000, remaining: 0x3F000, chosen: 0x1000
loc: 0x6000, remaining: 0x3E000, chosen: 0x1000
loc: 0x7000, remaining: 0x3D000, chosen: 0x1000
loc: 0x8000, remaining: 0x3C000, chosen: 0x8000 // 32k
loc: 0x10000, remaining: 0x34000, chosen: 0x10000 // 64k
loc: 0x20000, remaining: 0x24000, chosen: 0x10000
loc: 0x30000, remaining: 0x14000, chosen: 0x10000
loc: 0x40000, remaining: 0x4000, chosen: 0x1000 // back to 4k
loc: 0x41000, remaining: 0x3000, chosen: 0x1000
loc: 0x42000, remaining: 0x2000, chosen: 0x1000
loc: 0x43000, remaining: 0x1000, chosen: 0x1000

@Crzyrndm, the check should indeed be that the size is larger than the erase-block. Could you provide a PR ?

@Crzyrndm, the check should indeed be that the (remaining) size is larger or equal to the erase size. Could you provide a PR ?

PR has been opened. I think I got all the neccesary conventions covered but feel free to just fix it if more needs doing


Connection timeout

Hello there,
First of all congratulations for this nice piece of work.
I'm using Umami around a month now and upgraded recently to the latest version (1.24.1). Till yesterday everything was working smoothly, however from yesterday night Umami suddenly stopped working and any connection to Umami times out, both to the dashboard and the tracker (it stopped tracking visits).
This is what it outputs when I'm running the script manually (hoping to see any error messages):
$ npm run start

><EMAIL_ADDRESS>start /opt/projects/analytics/umami
> next start

ready - started server on <IP_ADDRESS>:3000, url: http://localhost:3000
info  - Loaded env from /opt/projects/analytics/umami/.env

I also checked all the subdirectories of Umami in case there's any log to troubleshoot, but found nothing. I neither found any log in the database (using MySQL) tables as well.
Restarting the service (and the whole server) didn't help either.
I understand I'm providing too generic information, if you can get an idea of what could suddenly happen, I would appreciate it.
If you need more info, let me know what should I provide and how/where to get it.
Thank you very much.

Before spending your time to look at this, I'll check first if there's any weird network issue happening suddenly on the server site, which may block connections.


is there a blog starter for this lib, similar to Ghost js?

Default setup will create you a base project with the default theme, so yes. Just follow the setup and you will end up with this

@MoOx  in regards to writing posts , will that have to be done in an development offline environment? I'm wondering if this is right for me. I have an existing React app and I wanted to add a blog to a subdomain.  I was going to have remote blog writers add the content(no web dev experience).

You can have a look to netlify with autodeploy per PR: people just add a markdown file and you get an online url to preview when build is done. No livepreview without dev env tho.

I own a blog too and I suggest that you should not use a static site generator for writer with no dev experience. You'll end up with many many issues like: teaching them how to use markdown, where to upload images, ...
IMHO, you should actually use Ghost.js if you want to have an ghost-like experience. If you still like a static site generator then hook Phenomic with Ghost's API

"Static CMS" are also an option...

 Most of them relies on Github backend and they create a commit mess :p

@thangngoc89 , @MoOx  Thanks, I was hoping to keep the entire App under the Firebase/Google Umbrella but It seems that deploying Ghost on Digital Ocean or AWS might be the right move for me. Surprised however, that there is not a Ghost like lib for react.  I may look into making one :)

Maybe take a look to next.js

Currently, I'm hosting 10 static blogs with Ghost as a backend on a $5 Digital Ocean droplet. So if you like the benefit of a static site generator and the UX of Ghost dashboard, I think you should give it a try.

@thangngoc89 are you using custom ghost image? I just checked Digitalocean and it requires minimum $10 droplet for the 1click install?

@jasan-s I install everything with SSH, I don't use the 1click install. As I said above, I only use Ghost as a private backend and pull data from it on each build, it rarely receives any traffic.


Redesign build to gradle

Just building from command line

Technically, it's allowable to gitignore the gradlew files too, as that's something the user can and should generate from the command-line or IDE.

gradle/* and gradlew - generated by gradle init
gradle/* and gradlew - it's need if gradle not installed in system
gradle/* and gradlew - gradlew will be download gradle expected version
(gradle/*.jar  is little and only for init download)
In the system can be installed gradle 2.1 but for build need 2.5 and in
this case user must run gradlew (for compatibility)

Best regards
Evgenii Sopov
https://github.com/sea-kg/
other e-mails<EMAIL_ADDRESS>skype: sea-kg
2016-07-22 16:08 GMT+07:00 Gregory<EMAIL_ADDRESS>
Technically, it's allowable to gitignore the gradlew files too, as that's
something the user can and should generate from the command-line or IDE.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/fesh0r/fernflower/pull/16#issuecomment-234493692, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABnf6A-woSwhsGUjMDLtrgdkEWbCRVF5ks5qYIiHgaJpZM4JSihW
.

Unofficial mirror of FernFlower Java decompiler (All pulls should be submitted upstream) - https://github.com/JetBrains/intellij-community/tree/master/plugins/java-decompiler/engine

You will need to create a pull request on the IntelliJ Community repository. This repository will automatically be updated when changes to the java-decompiler (fernflower) occur.

In the mean time, the following is a simplified gradle script that will build the application with the directories as they are, leaving the jar in build/libs/fernflower.jar:
apply plugin: 'java'

repositories {
  mavenCentral()
}

dependencies {
  testCompile 'junit:junit:4.12'
  testCompile group: 'org.assertj', name: 'assertj-core', version: '3.6.2'
}

sourceSets {
  main {
    java.srcDirs = ['src']
  }
  test {
    java.srcDirs = ['test']
  }
}

jar {
    manifest {
        attributes 'Main-Class': 'org.jetbrains.java.decompiler.main.decompiler.ConsoleDecompiler'
    }
}


Fixed keys should not need to be a subset of dynamic keys

Suggestion
I think it should be possible to have fixed properties on a dictionary that doesn't need to match the type of the generic ones, or the other way round: that generic values should not be a superset of the fixed values
🔍 Search Terms
dynamic keys, static keys, mixing static and dynamic keys
✅ Viability Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[ ] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion
So, in terms of code, I want to be able to type this:
type X = { startDate: string, [name: string]: number  }

However, typescript does not understand that the fixedKey startDate doesn't need to match the other generic key value pair, so you are forced to write it like this:
type X = { startDate: string, [name: string]: number| string }

💻 Use Cases
Adding dynamic keys to objects in javascript is quite common, and they don't need to match the type of existing keys. Many times you have a set of well known keys mixed with other dynamic keys, and you only care about the fixed ones and their type.
With destructuring is quite easy taking apart the known keys from the dynamic ones
const { fixedKey, knownKey, ...otherKeys} = someObject

So having all the "otherKeys" object have a mixed type just because fixedKey and knownKey didn't matched the type of the dynamic keys is an unnecessary trouble.

Indexed types with known properties are already unsound, and your suggestion would just worsen the situation by introducing the potential errors to not only the known properties, but to any properties accessed with the indexer.
const x: X = { startDate: "example" };

const key: string = "startDate";
x[key] = 123;

x.startDate; // Compile time type is string, runtime type is number;

But that is something the compiler should be able to catch. You already have the startDate as a constant string so it knows that you are trying to add an invalid type to a static defined prop.
But I see that, for some runtime values, you have no way to know if a string contains startDate or not.
Should this be possible using symbols then?

Duplicate #17867, #7765, others.
You can represent this with an intersection type instead.

Yes, it is a duplicate of those.
Sadly you can't use an intersection type for this. Sure, you can declare it, but you can not type anything with that value.


Forensics IAM Permission Denied trying to modify Instance Role

Under collecting evidence there is a section to modify the IAM permissions for the Node Role and add the policy below:
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": [
                "s3:PutObject",
                "s3:GetObject"
            ],
            "Resource": "arn:aws:s3:::clusterstack-forensicsbucket53bd3a1e-ub81jhk20uvk/*"
        }
    ]
}

When creating an inline policy or stand alone policy I am receiving the error below:

User: arn:aws:sts::775288309636:assumed-role/TeamRole/MasterKey is not authorized to perform: iam:CreatePolicy on resource: policy eks-S3upload

and

User: arn:aws:sts::775288309636:assumed-role/TeamRole/MasterKey is not authorized to perform: iam:PutRolePolicy on resource: role ClusterStack-ng1NodeGroupRole341A083C-JKSXZFE1UL88

looks like this may impact only the Console Role from the engine accounts, using the Pre-create Cloud9 Workspace I'm able to attach the policy just fine:

Create a file with the IAM policy above, i.e. S3-up.json

Add this as an inline policy on the Node instance role:

aws iam put-role-policy --role-name ClusterStack-ng1NodeGroupRole341A083C-JKSXZFE1UL88 --policy-name EKSS3 --policy-document file://S3-up.json

Update EC2 instance profile for node group/worker nodes to include write access to the forensics bucket.

Fixed in 5895c41


Add output to results

Some queries to vertica DB return additional output. For example:

42611: Using PARTITION expression that returns a Numeric value
Hint: This PARTITION expression may cause too many data partitions.  Use of an expression that returns a more accurate value, such as a regular VARCHAR or INT, is encouraged

This is very important to show them in results. I can see them in output tab, but it always hidden when switching to results. We can miss them

Agreed

I think that this can be solved by putting output panel (as well as execution log) to the right/down after the results.

Or move it to a separate view (like error log view)


Consider updating to a newer Sphinx and relaxing the constraints

Hi! It'd seem that sphinx.setup_command doesn't exist since 7.0:

https://github.com/sphinx-doc/sphinx/blob/v6.2.1/sphinx/setup_command.py
https://github.com/sphinx-doc/sphinx/tree/v7.0.0/sphinx/setup_command.py (doesn't exist)

In Nixpkgs, since opensfm's requirements.txt pin its dependencies to the patch versions (e.g. Sphinx==4.2.0), we've been just shipping opensfm with relaxed constraints, effectively dismissing the requirements.txt. Right now have to patch opensfm's setup.py ad hoc, so as to account for Sphinx's interface changes.
It'd seem however, there shouldn't be any particular reason for opensfm to keep sticking to the old version? Would it also be possible to consider pinning major or minor versions of the dependencies instead? Additionally, if these were pinned via the project.dependencies in pyproject.toml (cf. https://setuptools.pypa.io/en/latest/userguide/pyproject_config.html), the pep-517 frontends would automatically verify these constraints. Setuptools would also export all of that information in the .dist-info, which might be useful for other projects
Thanks!

Cf also https://github.com/sphinx-doc/sphinx/pull/11363


Enfoce min bid / send amount throughout app

Min bid / send amounts should be 0.00010000

Fixed in https://github.com/lbryio/lbry-android/commit/4a3db5ae20bf7e510014682fc6e3f9f67a662ba7.


Add this to bower

Could you place this into bower repository!?

yeah why not, give me a few days and I'll do it :)

Tks man! here is a link that will help you
https://bower.io/docs/creating-packages/#register

it's done
package name: overwatch-heroes-icon-font


Pooling allocator: make backend (mmap, uffd, memfd) runtime-configurable.

(Stacked on top of #3697)
Currently, the pooling allocator makes heavy use of compile-time
features to determine its runtime behavior and allocation strategy. This
makes testing harder, and makes runtime configuration from higher levels
of the system impossible.
This PR passes a PoolingBackend value down from the configuration
plumbing and into the pooling allocator, and uses its value to
dynamically choose a backend instead. This is mostly a matter of lots of
plumbing and conditionals.
The most complex part of this PR is actually the testing and feature
setup. We still want the memfd and uffd backends to be optional -- i.e.,
one should be able to build a wasmtime binary without them included.
This implies not including the enum options in the config enum, and
everything down from there.
In order to test all possible situations, we actually need to test four
builds -- with neither uffd nor memfd, with just one, or with both. We
also want to test that everything works when different backends are
specified, and the simplest way to do this is just to run the whole test
suite with the default backend set to each possible option. Hence we run
tests with both backends included and the default set three different
ways; with one backend included and the default set to that or the
allback mmap backend; etc.
I'm not sure that this is actually the simplest option -- it may, in the
end, be simpler to entirely remove uffd, if we eventually determine that
memfd supersedes it, and then unconditionally include memfd support on
Linux. But it was suggested here [1] to opt for a dynamic approach, so
this PR explores what that would look like!
[1] https://github.com/bytecodealliance/wasmtime/pull/3697#discussion_r792246996

@alexcrichton This is my exploration of what a "dynamic backend choice" might look like, as per your comment in the earlier review. I'm not entirely sure I like it -- it actually creates much more complexity passing through the backend choice everywhere, and it creates additional states to test (one backend included, but user has chosen another).
My intuition here is that simplicity is better found by just reducing the number of backends -- e.g. if/when we decide that memfd supersedes uffd, we can remove that, and then we can do memfd by default on Linux, and all of memfd is already built to support some memories having images and others not, so it should support dynamic fallback to mmap much more gracefully.
I'm also worried that since uffd was built as a static feature choice, I may have missed something somewhere that needs a dynamic branch -- this feels like a somewhat dangerous refactor.
Thoughts?

This has been superseded by #3778 (for memfd; and I think we're likely to remove uffd), so I'll go ahead and close this. Can bring it back if needed and we decide we want to keep uffd around with a dynamic switch.


Menu entry for Code generator doesn't appear in Android studio 1.2.2

No menu entry for code generator when right click on any layout file.

Thanks for the comment, I will try to use it as soon as I have time.
Could you please tell me if you are Mac, or Windows user.

Either Mac or Windows user. I tried it on a linux machine with xubuntu.
2015-07-21 14:48 GMT+03:00, Tomasz Morcinek<EMAIL_ADDRESS>
Thanks for the comment, I will try to use it as soon as I have time.
Could you please tell me if you are Mac, or Windows user.

Reply to this email directly or view it on GitHub:
https://github.com/tmorcinek/android-codegenerator-plugin-intellij/issues/17#issuecomment-123278870

Does the problem still occur in Android Studio 1.3?

Yes, still no menu entry for code generator appear when right clic on
layout file.
2015-08-05 18:09 GMT+03:00, Tomasz Morcinek<EMAIL_ADDRESS>
Does the problem still occur in Android Studio 1.3?

Reply to this email directly or view it on GitHub:
https://github.com/tmorcinek/android-codegenerator-plugin-intellij/issues/17#issuecomment-128031784

1.5 does not appear yet

Works fine in Android Studio 1.4 and 2.0
Maybe you not restart Android Studio after plugin installation?
Menu available after restarting and finishing gradle build

Android Studio 2.3 still does not appear

Android Studio 3.0.1 doesn't show option yet.


Cosmwasm Tracking Issue

Twap bindings

[ ] https://github.com/osmosis-labs/osmosis/pull/2212
[ ] https://github.com/osmosis-labs/bindings/pull/35

Enabling whitelisted Stargate queries

[ ] https://github.com/osmosis-labs/osmosis/pull/2190
[ ] https://github.com/osmosis-labs/wasmd/pull/7

Optional(tbd)

[ ] Support json encoding / decoding in stargate queries

Closing this issue per finishing all tasks


Update our documentation translations

I tried to update our docs in other languages by pulling the translations from Transifex, but I wasn't able because of permissions.
$ cd docs/
$ tx pull --all
tx INFO: New translations found for the following languages:ru, zh_CN, tr, zh, nl
tx INFO: Pulling translations for resource readthedocs-docs.api (source: locale/pot/api.pot)
tx INFO: Skipping 'fa' translation (file: locale/fa/LC_MESSAGES/api.po).
tx INFO: Skipping 'nb' translation (file: locale/nb/LC_MESSAGES/api.po).
tx INFO: Skipping 'ja' translation (file: locale/ja/LC_MESSAGES/api.po).
tx WARNING:  -> es: locale/es/LC_MESSAGES/api.po
tx ERROR: Forbidden
tx ERROR:
Error: Authentication failed. Please make sure your credentials are valid.
For more information, visit:
https://docs.transifex.com/client/client-configuration#-transifexrc.

@ericholscher @agjohnson can you grant me permissions for this?

:+1:

@agjohnson did you close it by mistake? If not, what was the reason?

I think @agjohnson already update the translations https://github.com/rtfd/readthedocs.org/pull/4645


Data Storage/Inscriptions

The goal in making these a paired set of OIPs is that we can define a minimal/permissive standard for data storage [..., OP_0, OP_IF, 0x03, "ABC", ..., OP_ENDIF, ...] while also carefully documenting the current rules about what ord considers to be a valid inscription.
This will form the basis needed for future third-party/application-specific development that utilizes this technique while avoiding undermining ord's place as the 'reference implementation'.
The current targeted design is that OIP 0004 will define a data storage transaction very loosely. Specifically, any input that includes as part of it's witnessData[1:] the following structure:

Any number of bytes to include signatures/etc, followed by OP_1, OP_IF
A pushed string (eg. "ord", "brc") representing which protocol/sub-protocol this data is attributed to
Any number of bytes, tags, or other content, followed by OP_ENDIF
While not encouraged, inclusion of additional data after closing the envelope will not result in invalidation

This sets a strong baseline condition that is easy to check for and should encompass all current use cases of this envelope type.
OIP 0005 will then seek to strictly define the structure of Inscriptions and other data storage attempts that utilize the 'ord' to enable full backwards compatibility from this superset of the standard to the current restricted envelope that is utilized by the ord client.
By separating these two we gain multiple technical benefits, but more importantly it establishes the baseline for future application-specific envelope development.

@Psifour, great initiative on setting this up. I think the issue of "carefully documenting the current rules about what ord considers to be a valid inscription" is top priority in Ordinals at the moment, with the ongoing discussion in https://github.com/tyjvazum/arb/issues/16, https://github.com/ordinals/ord/issues/2045, https://github.com/ordinals/ord/pull/2109, and https://github.com/ordinals/ord/discussions/2113.

I very much agree, but I also expand that beyond ord inscriptions as I actually feel that may not be the absolute strongest use case (as you seem to agree with arb if I am reading your docs right).
We both seem to have come to similar ideas that the documentation should be a super-set of the possible designs/implementation and then restricted at an application-specific level. Very excited to have your eyes on this and hope we can arrive at documentation that will support and encourage development on top of the really effective set of rules that Casey pioneered.

Yes, I think we seem to be very much in agreement.
I've implemented the concept of an Envelope Expansion, where inscription content and associated data is placed inside of a JSON wrapper that allows for backward-compatible upgrades. This was decided to avoid potential conflicts with the tag mechanism, to make integration with external tooling easier, and to enable automatic support in explorers, if only minimally, by displaying the JSON. It supports versioned subprotocols, specified in the JSON, and arb supports two top-level envelope protocols, ord and pub, which lacks sat tracking to enable use cases that don't require NFT functionality, of which I think there are many.
I see sat tracking as being the meaningful difference at the top-level (ord/pub) and I consider protocols like BRC-20, for example, to be a subprotocol of the ord protocol since it makes use of the sat tracking feature.
I'm quite interested in your thoughts on everything and look forward to participating in your documentation effort 👍

@HGraphPunks is interested in an OIP process too and started a discussion at https://github.com/ordinals/ord/discussions/2156. Perhaps we can plan some next steps here so everyone can work together in a coordinated way. There seems to be significant attention to the need for standardization in the space right now.


chore: Replace U+00a0 with proper spaces

@bendiknesbo will you create a new release?

No, the workflow is working fine, even with U+00a0, so there is no need to cause dependabot-noise in "every" repo, when there is nothing that has actually changed for the consumers.

Scratch that. There were other commits that had not been released yet, so I created a release anyway :)


Run lint/Clippy first before build in GH actions

Most of the time, PR is broken because of formatting and/or Clippy issues. Therefore, it is desirable to run these checks first and get the feedback earlier before running builds and tests. My observation (likely biased towards my own behavior) is that we rarely submit code that does not compile or tests that are broken.

Yes, this is the correct ordering - fmt is also very fast.
A reminder to those watching that installing the pre-commit hook is a good way to avoid most build failures.