An actor model

I'll speak to what I feel to be the real elephant in the room for me for server development these days.
We need convenient multi-process, and web workers just don't cut it.
I know, everyone loves promises and async and generators and so on.  They'll point out that that's parallelism of a form.
It's still happening on one core, though.

Old man onion-on-belt story mode.
C++ has a difference between "containers" and "datastructures."  Containers are about how you use them; datastructures are about how they're implemented.  When you say something like "a map could be a red-black tree or an AVL tree," map is the container, red-black tree is the datastructure, and suddenly heap becomes intensely confusing in conversation (especially once you start talking memory management.)
Lots of people get bent out of shape about how it would be implemented, what the goals and limitations are, blah blah.  By metaphor, I think to the C++ crowd those are datastructure topics, and we need by metaphor to have a container discussion.
Fundamentally, it doesn't matter how they're implemented.  At least, not at the language level.

Look to erlang, f#, d, scala, akka, cloud haskell, CAF, and so on.
Each has a programming language level model for parallelism and multiple fundamentally different backend implementations with trade-offs.
Why?
Because the language was able to offer to the programmer the tool, without forcing the implementation's hand.
Look to C++.  The specification for map<> gives extremely detailed performance guarantees, but still, many STL vendors use many different implementation backends.
These things can be done in a way that doesn't nail down how they work, but does nail down how they're used, and how they're kept secure.
Sometimes - oftentimes - that's best, and easiest to get finished.

An actual developer-friendly implementation doesn't even need processes or threads underneath (though that is the sensible choice, and the intended goal.)  This can easily be implemented in a single thread as what amounts to cooperative or pre-emptive multitasking, while waiting for a deeper implementation.
erlang's parallelism model is the easiest to understand and work with that I have ever seen, bar none, full stop.
Here's a quick, bastardized JS version:

Introduce a new type, the pid, or 'process id', which represents a process
A function self() that produces the current pid
A way to stall.  This could be yield.  Erlang generally handles this by blocking on receive, described below.
spawn({ initial_function, args, host_node }) -> pid

those options:

initial_function is the main() of the process
you guessed what args are
host_node is for a multi-node vm, and would be unsupported on most impls

you could add:

links to notify when the process threw, bidirectionally
links to notify when the process threw, monodirectionally
registered_name for a global lookup

when initial_function terminates, the process does too
the main process is a pid now
you send messages between pids to communicate between them

messages are immutable plain data.  no functions, no UDTs, no nonsense, just JSON and maps and sets
no, processes may not pass references between one another.  an exception is made for PIDs.

you could introduce a new function to send to a pid, but erlang uses an operator !, and i like that, so this example will use that
you introduce a new operator receive to receive a message, which has a very case-like structure, pattern matching against what it receives.

a well-written receive will discard messages it can't match, but they don't imply that because there are tricky things you might be doing instead, in the way that break isn't implied in case because you might be doing duff's device.  even though you aren't, it's just a bug
operator receive needs to block for free, because that's how almost all threads are going to do what a generator person thinks of as yielding

processes must be kept ridiculously lightweight (think what java calls green threads.)  if we're going to throw a lot of these around, the lower the cost, the better.  erlang gets a process in under a K with zero idle cost
if a process faults, let it fault.  move on.

craptacular half-baked example time:
const targets = ['www.ibm.com', 'www.microsoft.com', 'goatse.cx'],

      fetch_p = ({ url, mgr }) =>
        // this will end up happening in some other pid
        fetch(url).then(
          data => mgr ! { site: url, result: data.json() }
        ),

      pids = targets.map(
        // this is what makes and sends-to the other pid
        addr => spawn(fetch_p, [{ url: addr, mgr: self() }])
      );

const recv_left = targets.length;
let   results   = {};

while (recv_left) {

  receive {

    case { url, result }:
      results[url] = result;
      --recv_left;
      break;

  } after 5000 {
    throw new ReceiveException("Timed out");
  };

}

not sure but i think that this is enough to get browsers and node on board despite their wildly different multiprocessing needs, and is also enough to get erlang going through 20 years of being the best parallelism in the game
i think it's a decent place to start looking for answers
this also really heavily says "hey guys and gals, remember tail recursion?"

I suppose there's also a decent argument for doing this by pushing a promise, but that involves so many changes to references and how a closure would work that I don't even slightly want to think about it

I really wish you'd stop closing my tickets, dan

I would like this ticket reopened.  I stand by the suggestion.  It is correct, appropriate, and should be considered.  It does not belong on #16.

It is a bit difficult to have a focused discussion in #16. At some point, each idea of merit deserves a focused issue, where the idea can be further explored. I believe it is a bit premature to close this issue and similar ideas before there is a significant comment period.

@brylie Please have a look at the README:

The goal of this proposal is to define a mechanism for providing a more extensive standard library in JavaScript than is currently available.
The library itself is tangential to this proposal, and would be built and expanded upon in later efforts. Such a library would only cover features which would be useful in JavaScript in general, not things which are tied to the web platform.

This repo is for "How could a standard library be integrated in JavaScript", the contents of the standard library are all their own proposals, like https://github.com/WICG/kv-storage, the discussion here is only to help determine what the shape could be in the future.


opencl/Makefile.am

AM_CPPFLAGS += ... $(OPENCL_CFLAGS)
@jbarlow83, @stweil, from where it gets $(OPENCL_CFLAGS)?

That macro is not set, so it is empty (unless someone sets a value when calling make).
Normally, a PKG_CHECK_MODULES test for OpenCL in configure.ac would set the macro, but the current implementation does not use PKG_CHECK_MODULES for OpenCL.
In most cases the build works even with the wrong macro (that's why I never noticed it).


[XL] Reorganize lenses in separated repositories.

This task also deprecates the lens-selector service to a new structure in lenses organization.

The contents of this repository will be developed in #15

@aalonsolopez done right?

Yes


多gpu 分词报错

使用的是这个 模型 hanlp.load(hanlp.pretrained.tok.MSR_TOK_ELECTRA_BASE_CRF,devices=[0,1,2,3,4,5,6,7])

[auto-reply] Thanks for your comment. However, the essential information is required. Please carefully fill out the form when open a new issue.


[Front-1762] Increase start game time

Motivation
Since we are adding the screen to select a bounty before the match we need to increase the start of game delay.
Summary of changes
Increased the start_game_time_ms by 5000 milliseconds.
How to test it?
Play the game with this branch and this front PR
Checklist

[x] Tested the changes locally.
[x] Reviewed the changes on GitHub, line by line.
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

Cosed since this change is already being done on #655


Run calculator should allow equals sign at the end for calculator results

Description of the new feature / enhancement
I'm not sure if my configurations are wrong or there's a bug, but if I input a calculator query that has a equals sign = at the end, I get a result for "Search the web" instead of the calculator result I would have expected.
For example 1+1=

But with 1+1 I definitely get a calculator result.

Scenario when this would be used?
I expect a lot of people typing maths queries into PowerToys Run will use an equals sign at the end expecting it to return the maths result, rather than leading them to a search query.
Supporting information
There are my PowerToys Run configurations, which I believe to be standard/defaults.

Hello and thanks for your message. The "direct activation character " is supposed to be at the beginning of the query 🙂

Jay-o-Way is right, you need to start the query with "=" :)

I appreciate that the direct activation command feature expects an equals character at the start, but I think there's some confusion about the intention of this issue.
In my scenario, "include in global result" is selected which means "Show results on queries without direct activation command" applies.
For this scenario, I'm confused why adding an equals sign at the end of the query, which is how I imagine a lot of people type maths equations, breaks the expected t of the calculator to provide a result.

I see. Well, the most quick and simple answer would be "that's just how it works". Thing is, you can choose/set any string of characters. So, while "=" is logical because of the context, that logic fails for any other character/string. In a broader perspective, using the special character(s) at the beginning are a way to "specify" a specific plugin, followed by the input.

I'm confused as to why folks think typing the activation character = anywhere else and failing is OK. Seems like bad UX.

@cinnamon-msft Can we get this reopened? This wasn't a user support scenario.


Using the beta 'stages' feature of Travis

This should launch the three stages in parallel. It also isolates just the python setup.py install to docker. The other tests don't need to be run in docker.
It should be noted that a failure in the first stage will fail the other stages.

I'm wondering if it is helpful to still run the tests in docker. This will ensure that the appropriate dependencies are in place, including protos.

I don't see how running pylint and unittests need to be run inside the container. I'm happy to switch back, but I think we gain some efficiencies here.
The docker container test still ensures everything is (consistently) built with the same dependencies.

Adding cla: yes label, as the PR author is a googler at the time of this PR was created.


Faster startup in case of initialization error + more verbose logs

This PR makes the startup faster and more verbose in case of initialization error (e.g. peer not in channel yet)

Catch any exception in the app initialization (register-node) and log it.

If an exception occurs in the initial ledger call, always retry it forever and never crash the app. This is faster than crashing the pod and waiting for it to restart. Note that kubernetes will still crash the pod if the readiness probe fails (i.e. initialization repeatedly fails for > 30 secs or so)

With the log-master=true option, no logs are output until the app initialization is complete or the pod is crashed. In other words, if the app initialization takes a long time, we can't see the logs until either the initialization finally succeeds, or the container is stopped by kubernetes.

...wait...
...wait more...
...what is going on?....
After a good 30 seconds all the logs arrive at once

This PR removes this option.

e2e tests :heavy_check_mark:


A few suggestions

Category

[x] fzf binary
[ ] fzf-tmux script
[ ] Key bindings
[ ] Completion
[ ] Vim
[ ] Neovim
[ ] Etc.

OS

[ ] Linux
[x] Mac OS X
[ ] Windows
[ ] Etc.

Shell

[] bash
[x] zsh
[ ] fish

file list caching
It seems that fzf load file list every time from scratch.
Ctrl-t in my home directory, there are almost 2M files and it takes almost 2 minutes.
I hope file list caching will be added.

filter or exclude pattern
When I am in my home directory, I rarely want to search files in Applications/ or Library/.
How about reading exclude pattern in fzf conf file something like this?

$ cat > ~/.fzf.conf
exclude Applications/
exclude Library/

Ctrl-t like Ctrl-r
I think this is a natural usage, but it won't work that I expected.

$ vi some/parent/dir/<Ctrl-t>

I expected that fzf would show files under some/parent/dir/ or its descendant dirs.
Furthermore, It would be very handy if fzf supports auto-completion like this:
$ vi s/p/d/<Ctrl-t>

caching was already discussed in previous issues, it's outside the scope of fzf which is just a filter, not a source and not a source management system.
FZF_DEFAULT_OPTS and other env vars exist for that purpose. Use your normal shell rc or vimrc.

@justinmk With 1. and 2., what I am trying to tell you is how to speed up loading file list with exclude pattern, not the how to filter out some exclude pattern within file list.
I have checked the fzf man page, but I can't find how I can set the exclude pattern.
Please tell me what I have misunderstood.

I totally agree with you on 3. I've always missed that and it felt very natural to have such a behavior. Maybe it could be made configurable (something you can turn off).

Thanks for the suggestion.
Regarding point 1 and 2, let me put it this way: fzf can be thought of as an interactive version of grep. Does grep cache the input? No. And grep does know the meaning of the text it's processing. It's designed to "not care" about the context. The same can be said about fzf.
seq 1000 | fzf
git tag | fzf
ps -ef | fzf
find . | fzf

You see, fzf cannot decide whether if it makes sense to cache the input, or if some extra pre-filtering is appropriate or not. It all depends on the context but fzf is designed to be a context-free filter just like grep. So in that sense, it's beyond the scope of this project.
What you can do instead is to write a script that caches the output of find and use it as the input to fzf. The users should know better about their systems and their needs.
find-cached | filter-irrelevant | fzf

# or
export FZF_DEFAULT_COMMAND='fzf-cached | filter-irrelevant'
fzf

(There's also $FZF_CTRL_T_COMMAND.)
Many users including myself use ag as their FZF_DEFAULT_COMMAND:
export FZF_DEFAULT_COMMAND='ag --hidden --ignore .git -g ""'

ag also allows you to extend its filtering rule with .agignore file, so you might want to check it out.
https://github.com/ggreer/the_silver_searcher/wiki/Advanced-Usage
The behavior you described in point 3 is available via fuzzy completion (vim some/parent/dir/**<tab>) and if you use zsh, you can configure CTRL-T to act as the dedicated key for fuzzy completion. You can find the details in this page.

$ vi s/p/d/

I'm not against the idea as long as we can have the same behavior both on bash and zsh (I myself am a bash user). Pull requests are appreciated.

The behavior you described in point 3 is available via fuzzy completion (vim some/parent/dir/**)

Wow, didn't know that! That helps a lot, thank you!

@junegunn Thank you for your kind reply.
I agree with the point that fzf binary should remain in the same scope with grep.
But grep doesn't do key binding such as Ctrl-t or Ctrl-r.
I thought the functionalities could be added as shell integration extensions.
I have switched from bash into zsh, and I realized how handy tab completions are.
I think vi s/p/d/<Ctrl-t> is much cooler than vi some/parent/dir/**<tab>.
Anyway, I'll try more configurations that you suggested.
And thank you for fzf.

@dongminkim Yeah I see your point, but they are optional and not the core part of the project. They are there to give you the idea of how fzf can be used to extend the functionality of shell and to get you started with fzf, but I don't plan to add more to them.


Fix Wrong argument name

Hey! thank you for making this plugin I face this issue and then decide to make pull request
I get right argument name from this Document:
https://github.com/pyrochlore/obsidian-tracker/blob/master/docs/InputParameters.md

Thanks for pointing it out and the fix.


✨ Mobile | All users can be scanned

Cc: @matt-goldman @zacharykeeping @Anton-Polkanov

Hi @tkapa
Pain

Related: #561
Blocks: #740
Currently only SSW Users are Scannable in the application. In order to implement the "Other" filter for this application, all users need to have their own QR Code that grants the user an achievement.
Suggested Solution

All users should have an achievement associated with meeting them. External users should have a lower point value (~100).
Tasks

[x] Investigate
[x] Implement

Acceptance Criteria

[x] Meets Definition of Done - {{ LINK }}
[ ] External users can be scanned in the application

Thanks!

Done - this has been implemented by Matt.


Table gets scrambled when viewing the details

Steps to reproduce:

open an ultimate comparison (eg. https://ultimate-comparisons.github.io/ultimate-IoT-platform-comparison/)
open the details of any item
watch the table get scrambled in the background

This only happens if the table is not ordered specifically (ie clicking on the header).
This also doesn't happen with the base example.
When fixing #23 this should be fixed as an side effect.

Is this issue still valid?

Nope, it has already been fixed.


Problem of Running distributed version

@lespeholt
Can distributed version use local server instead of GCP?Looking forward to your reply：）

Yes. The local script in the readme runs the actors and learner in separate processes.

Yes. The local script in the readme runs the actors and learner in separate processes.

Yes. The local script in the readme runs the actors and learner in separate processes.

Is there a document reference to deploy SEED RL on our own server instead of using GCP, README.md has no relevant information, thank you very much

Yes. The local script in the readme runs the actors and learner in separate processes.

Is there a document reference to deploy SEED RL on our own server instead of using GCP, README.md has no relevant information, thank you very much

THe same  question with Crazyalltnt.
@lespeholt

THe same  question with Crazyalltnt.
@lespeholt

server_address can be changed here: https://github.com/google-research/seed_rl/blob/master/common/common_flags.py#L23
it can also be set to e.g. unix:/tmp/agent_grpc for using Unix domain sockets instead of the network stack.
Other than that, you see the flags applied in the docker file:
https://github.com/google-research/seed_rl/blob/master/docker/run.sh#L52

server_address can be changed here: https://github.com/google-research/seed_rl/blob/master/common/common_flags.py#L23
it can also be set to e.g. unix:/tmp/agent_grpc for using Unix domain sockets instead of the network stack.
Other than that, you see the flags applied in the docker file:
https://github.com/google-research/seed_rl/blob/master/docker/run.sh#L52

Hi @Crazyalltnt @Maxwell2017  when you refer to local machine do you mean GPU or just a single CPU?

I mean local servers, not cloud servers

Hi @Maxwell2017 ,ok thank you. do you know if I can run this SEED_RL on a single CPU?

@Pranav-India Sorry to reply you so late, I think it can run on cpu machine. However, the learner generally runs on gpu. If you use cpu, the distributed acceleration effect may not be achieved.

@Pranav-India Sorry to reply you so late, I think it can run on cpu machine. However, the learner generally runs on gpu. If you use cpu, the distributed acceleration effect may not be achieved.


[discussion] Support of maven project, modules, parent

Discussion
This ticket list the different maven project combinations and the problems that currently we must resolve
1. Multiple independent components under a single git repo without a parent pom
demo
  .git
  .mvn
  fruit-backend-sb
  fruit-client-sb
  mvnw

Binary push: OK
Source push: OK
Build mode: KO because of the s2i following problem as a pom.xml is needed within the /path of the project

2. Multi-module maven project under a single parent
demo
  .git
  .mvn
  fruit-backend-sb
  fruit-client-sb
  mvnw
  pom.xml

Binary push: OK
Source push: KO as parent pom doesn't get pushed along with the module code and therefore maven
cannot build (unless parent is already published in a publicly available maven repo)
Build mode: OK

3. Multi-module maven project under a single parent
Remark: The children don't reference the parent (BAD organization in terms of maven project)
demo
  .git
  .mvn
  fruit-backend-sb  // The children don't reference the parent
  fruit-client-sb       // The children don't reference the parent
  mvnw
  pom.xml

Binary push: OK
Source push: OK as parent pom doesn't exist for all intent and purposes of building the children
modules. However, this can only work if nothing in the parent is needed by the children (though
the same would happen with a regular maven build)
Build mode: OK

I propose that we only support project structure 1. and 2.. Make sense @metacosm ?

For project type2, this is I think the responsibility of the CLI tool to push in this case the project with : pom.xml, moduleA, moduleB,....,moduleX. WDYT @metacosm ?

I agree that we should only support types 1 and 2 since these are the logical organizations that people are likely to use. We should also support the most common use case which is: single module per git repo.

For project type2, this is I think the responsibility of the CLI tool to push in this case the project with : pom.xml, moduleA, moduleB,....,moduleX. WDYT @metacosm ?

I'm not sure as this means that some of the intelligence needs to move to the client and I think that the operator should actually handle that case. That said, I'm not sure what can be done without the client informing the operator about it. I really don't like this because that means having to handle special cases in the client. Then if consider that's only one special case among possibly many for different build systems and you start to see why I don't really like opening this Pandora's box.

That said, I'm not sure what can be done without the client informing the operator about it.

Even if the client informs the operator, all the code should be pushed or at least the module plus  the parent pom.xml

That said, I'm not sure what can be done without the client informing the operator about it.

Even if the client informs the operator, all the code should be pushed or at least the module plus the parent pom.xml

And that's exactly what I would like to avoid because that requires the client to know about maven (and gradle, and npm and…)

Something else to be considered is :

Do we want to continue to use the s2i image which suffers from the limitation or restriction that a pom.xml is needed at the root of the project from where mvn is executed OR
That we use too for the Tekton build our mvn-jdk image where we can define the contextDir and moduleName OR
That we use JIB to build the image from the code source

And that's exactly what I would like to avoid because that requires the client to know about maven (and gradle, and npm and…). Problem is: I'm not sure how to make it work otherwise… :(

The only solution that I see is to ask a question to the developer with the CLI in order to know if this is :

A maven project with only one module -> 1 component
A maven project with several modules + parent -> x components
A maven project with several modules without pa rent -> not supported

And that's exactly what I would like to avoid because that requires the client to know about maven (and gradle, and npm and…). Problem is: I'm not sure how to make it work otherwise… :(

The only solution that I see is to ask a question to the developer with the CLI in order to know if this is :
* A maven project with only one module -> 1 component

* A maven project with several modules + parent -> x components

* A maven project with several modules without pa rent -> not supported

This still requires the client to know about maven…


Automated cherry pick of #3343: fix: 避免update存储tag信息异常

Cherry pick of #3343 on release/2.11.
#3343: fix: 避免update存储tag信息异常

Codecov Report

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

@@              Coverage Diff               @@
##             release/2.11   #3345   +/-   ##
==============================================
  Coverage                ?   7.14%
==============================================
  Files                   ?     476
  Lines                   ?   77222
  Branches                ?       0
==============================================
  Hits                    ?    5516
  Misses                  ?   71243
  Partials                ?     463

Flag
Coverage Δ

#aFlag
7.14% <ø> (?)

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 a186a2b...6aa482c. Read the comment docs.

/lgtm

/approve


ubuntu 20 possible install issue with puppeteer ?

I am following precisely the installation instructions on a fresh instance of Ubuntu 20, I am getting an error in the 'npm install' phase (when npm tries to install  puppeteer@3.3.0).
Even if 'npm install' looks like to have failed in some way (see logs below), 'npm start' has started the web app.
My question is: is<EMAIL_ADDRESS>absolutely necessary or does nodetube work the same?
I have just started playing around with nodetube, thank you for the great work.
final log from 'npm install'

<EMAIL_ADDRESS>install /home/marco/nodetube/node_modules/puppeteer
node install.js

/home/marco/nodetube/node_modules/puppeteer/install.js:175
} catch {
^
SyntaxError: Unexpected token {
at createScript (vm.js:80:10)
at Object.runInThisContext (vm.js:139:10)
at Module._compile (module.js:617:28)
at Object.Module._extensions..js (module.js:664:10)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Function.Module.runMain (module.js:694:10)
at startup (bootstrap_node.js:204:16)
at bootstrap_node.js:625:3
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/@ffmpeg-installer/darwin-x64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"x64"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/@ffmpeg-installer/linux-arm):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"linux","arch":"arm"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/@ffmpeg-installer/linux-arm64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"linux","arch":"arm64"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/@ffmpeg-installer/linux-ia32):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"linux","arch":"ia32"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/@ffmpeg-installer/win32-ia32):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"win32","arch":"ia32"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/@ffmpeg-installer/win32-x64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"win32","arch":"x64"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/mocha/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: node install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Yeah sorry the Node version needs to be 10+ now, I'll update that thanks

I got rid of that module. If you pull the latest code it should work on Node 8 again. Thanks for the heads up.


[Event Request] table 37 "Sales Line" - field "Location Code" - OnAfterValidateLocationCode

Please add an Event OnAfterValidateLocationCode in field "Location Code" in table 37 "Sales Line"
        field(7; "Location Code"; Code[10])
        {
            Caption = 'Location Code';
            TableRelation = Location WHERE("Use As In-Transit" = CONST(false));

            trigger OnValidate()
            var
                IsHandled: Boolean;
            begin
			    ...
                OnAfterValidateLocationCode(Rec,xRec); <-- NEW EVENT
            end;
        }

    [IntegrationEvent(true, false)]
    local procedure OnAfterValidateLocationCode(PurchaseLine: Record "Purchase Line"; xPurchaseLine: Record "Purchase Line")
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 45914.


POST-Requests never finish

Hey, it's me again ;D
I work around this by using method=GET for my forms for now, but i spent 1 day debugging this, took a look into router.php (noice internal parameter array key!!) and even made sure i don't include a page with the same name as an included file (had login.php for both the page and the check).
Soooo i guess _POST request just don't work in dev, it's totally fine on apache2.
Steps to reproduce:
<?php
print_r($_POST);
?>

<form action="?" method="POST">
<input type="text" name="test" value="test"/>
<input type="submit" name="submit" value="submit"/>
</form>

never loads the page. Restarted the server, etc. - nothing. method="GET" works ootb

Interesting issue!
Will definitely look into that ASAP; I am glad someone is using my plugin almost as active or even more then me :D

It's a total breeze developing with this, i have best security with server backend and can handle xml to typescript now fine.
https://www.techempower.com/benchmarks/ still has nginx-php-mysql/postgresql at 300.000 of 600.000 best (rust/c) so more people should use this, you can get interpreter languages, best security and speed at 50% c-level. If you take a look at frameworks like laravel or rubyonrails your plugin is like 100 times faster.
top 1 post yesterday on hackernews: https://news.ycombinator.com/item?id=41469040
Maybe do a show HN there when most bugs are gone?

So, this critical bug is fixed now!
Yeah, PHP still rules, hence the plugin ;)
A bigger announcement especially on HN would definitely be beneficial! And I think the plugin is now getting almost to the point of being pretty stable and usable for development 💪🏼

What news to wake up to :D I updated and it works like a charm! I tried to make sense of the middleware as $_FILES is still empty, but it looks like a lot of bending vite to make it work and i was mostly interested in not having to workaround between deployments, can use method=POST in both and don't need to clean the URL by script.
I should, and most coders will, implement TS for uploads anyway.
There are sometimes missing line-numbers in errors, as everything is fed through the router, but this mostly an issue in bigger refactorings when it's not clear where one missed to fix a variable name, etc.
Warning: Undefined variable $nonexistant in /krei.se/node_modules/vite-plugin-php/dist/router.php(37) : eval()'d code on line 286

I think this will be known to other developers that this is not a fault of the plugin, but i modified router.php to catch warnings as errors and print out a more detailed stack trace with the correct sourceFile:
(function () {

        set_error_handler(function ($errno, $errstr, $errfile, $errline) {
                // Throw an ErrorException so it can be caught by the try-catch block
                throw new \ErrorException($errstr, 0, $errno, $errfile, $errline);
        });

	try {
		eval('?> ' . func_get_arg(0) . ' <?php');
		die();
	} catch (\Throwable $th) {
		die(
                        "Error: " . $th->getMessage() . "
" .
                        "In file: " . func_get_arg(1) . "
" .
                        "On line: " . $th->getLine() . "
" .
                        "Stack trace:
" . $th->getTraceAsString() . "
"
                );
	}
})($source, $sourceFile);

All in all i would say this plugin is quite ready to be used - the most important aspect for me is the ease of file copying to the compiled app without the need for vite-static-copy, etc.
I will continue working on my project, if you ever start to like it, feel free to list it as a reference and thanks for the instant resolution of those annoyances!


Throwing console.warn if no model path

Don't hate me amigo - but can you add a test with this?

Also, can you add a note in the Readme here?
https://github.com/infinitered/nsfwjs?tab=readme-ov-file#production

Looks great!


Clean up missing data in CSV file

The CSV file that backs the website could use some serious love. Give it the time it deserves and rebuild.

Done


Support range of temperature sensors

Need support for more than just Dallas One Wire temperature sensors, including but not limited to average/mean of a number of sensors.

Currently supports Dallas One Wire DS18B20
Highly desirable to also support Analog temperature sensors such as TMP36
Highly desirable to also support I2C sensors such as TMP007, MCP9808
Desirable to support custom interface sensors such as DHT22 and  SHT10

SHT10 has a Python library https://pypi.python.org/pypi/sht-sensor/
Adafruit have a DHT library https://github.com/adafruit/Adafruit_Python_DHT


Hpatches

Hi author, I would like to ask what training set the weights provided in github? I used the weights provided in github to test on the Hpatches dataset and found that it did not match very well in images with Viewpoint, may I ask what dataset you used to train the weights for testing on the Hpatches dataset?

The weights we provide were pre-trained on images from the 1M distractor images of https://github.com/filipradenovic/revisitop, then fine-tuned on MegaDepth.
Do you have examples of pairs of images of HPatches where it does not work so well? It should have a decent performance there, except for images with large rotations (eg > 45 degrees).

Yes, image 5 has almost a 90 degrees rotation compared to image 1. GlueStick was only trained for small rotations, so it cannot cope with such big rotations. When you know that your application will have rotation, you can always rotate one of the two images by 90 degrees several time and match the first image with the second one rotated at 0, 90, 180 and 270 degrees.

Ok, I will go and try to do some rotation pre-processing, thanks for your patience


Add a feature on the history logs to allow download in csv

Description
Add a feature on the history logs to allow download in csv Backend documentation
How to do

The first step is checked the following route https://github.com/ta-vivo/ta-vivo-api/blob/1f70ef899799f512a768fbc9ea5f4e039bd93cf3/src/routes/Check.js#L9
The proposal is creating other route like the router.get('/:id/logs') but with a extra parameter to indicate the file download, for example router.get('/:id/logs/download')
The response need the header "Content-Type", "text/csv"

I can work on this. Please assign it to me

Done https://github.com/ta-vivo/ta-vivo-api/pull/91


Include reference to view or procedure that will show these properties

Please add references to any stored procedures or "system" views that will allow these properties to be retrieved.

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

ID: 4cd48b72-0326-a279-7ff4-f0ddad982d88
Version Independent ID: 9af67e3e-4851-82d6-636d-573308d86f56
Content: SQL Server Agent Properties (History Page) - SQL Server
Content Source: docs/ssms/agent/sql-server-agent-properties-history-page.md
Product: sql
Technology: ssms
GitHub Login: @markingmyname
Microsoft Alias: maghan

@Cornan Hello, You can probably discover this information by using the the extended event (XEvent) that is described in the following How-To article, namely 'sql_statement_completed'. Establish and activate the xevent, and then operate the SQL Agent.  Then go see what the xevent captured.

https://docs.microsoft.com/sql/relational-databases/extended-events/quick-start-extended-events-in-sql-server

https://docs.microsoft.com/sql/relational-databases/extended-events/quick-start-extended-events-in-sql-server

I am now closing this Issue 2384. We hope to hear from you again.
CC, FYI: @markingmyname
. .


Freezing related to Latency ???

I've been doing like 10 games so far and I notied my latency was below 60 most of the time and I even had youtube open and everything (shitty computer) and I didn't froze once.

latency is the basic ping/ms that surviv.io sends and it has mostly nothing to do with freezing. Is your zoom and tree transparency disabled?

Does anyone have a solution? it's freezing too much

@1tarko get a new hack kid, or watch the videos that are in a older post

@humphreygaming Which old post? Can you explain me in the discord? skillz#1415

@1tarko this one is the old post: https://github.com/Kalaborative/survivio-plus/issues/315
Yes, i can further explain my statement. Accept the discord friend request


fancier dev tools

Ace editor for full control over input JSON, including copy-paste in and out.
lazy-loading inspector for _fullData and _fullLayout to be able to drill into circular structures

well, looks good 💃 except maybe that little state typo for currentMockIndex?


add ability to add external parameters for optimizer

With this pull-request we add ability to add external parameters for a custom optimizer

Hello @valer1435! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file test/unit/optimizer/test_external.py:

Line 76:1: W391 blank line at end of file


How to convert the m4a format to wav format?

While install the sdk via ios i couldnt able to the wav format but dragging the file and replacing its get working


Spreading a type marks the type's properties as possibly undefined

Not sure if I'm misunderstanding the intended behavior here, but I thought this would work:
/* @flow */

type x = {
   a(): Promise<any>
};

type y = {
   ...x
}

function foo(x: y) {
  return x.a()
}

12:   return x.a()             ^ call of method `a`. Function cannot be called on possibly undefined value
4:    a(): Promise<any>      ^ undefined

https://flow.org/try/#0PQKgBAAgZgNg9gdzCYAoVAXAngBwKZgAeYAvGAN6pjUCGAFAJQBcYACgE5wC2AlgM54APDQB2WAHyoAvgG502fGCykKVagDpNhaeigBXEQGMMPOCLBQ4cOoRZYGq6uzwY97c4XX0GOoA

Nevermind, just saw https://github.com/facebook/flow/issues/3666 - will wait for docs here

The fix is to wrap all spreads with $Exact like this:
type y = {
   ...$Exact<x>
}


Defining maximum payload size

Is your feature request related to a problem? Please describe.
At the moment the maximum payload size is 32MB for API and communication between flow and Knative services. This should be a configurable value and start wit ha lower value like 4MB. This makes the limit increase a conscious decision. 32MB as default seems to be quite high and dangerous in high-load situations.

It should be a configurable value in helm chart


Porterchester

new school YTI Career Institute
https://yti.edu/programs/computer-programs

@JMBGaming Thank you for your patience while waiting for a review and processing your request. Pull request merged. Please start applying for JetBrains educational subscription at https://www.jetbrains.com/shop/eform/students in an hour, to allow the changes to propagate through JetBrains systems.


Fix index bug for flag command

There was a bug where if the number provided in the input was too large, the wrong error message will be shown, particularly for commands that make use of indexes.
This problem was caused by bad error handling. If a ParseException is thrown by ParserUtil, flag command (and any of the other commands for that matter), will catch that exception and rethrow a generic exception.
Flag command now adds the underlying exception message from ParserUtil with the the generic error message.
Resolves #178

Apologies need to fix the test cases first before this can be approved.

Codecov Report

Merging #231 (bdd5f1c) into master (233fca7) will decrease coverage by 0.19%.
The diff coverage is 54.54%.

@@             Coverage Diff              @@
##             master     #231      +/-   ##
============================================
- Coverage     72.10%   71.91%   -0.20%
- Complexity      552      554       +2
============================================
  Files            89       89
  Lines          1660     1670      +10
  Branches        189      192       +3
============================================
+ Hits           1197     1201       +4
- Misses          401      404       +3
- Partials         62       65       +3

Impacted Files
Coverage Δ

...eedu/linkedout/logic/parser/FlagCommandParser.java
0.00% <0.00%> (ø)

.../java/seedu/linkedout/logic/parser/ParserUtil.java
83.63% <50.00%> (-6.56%)
:arrow_down:

.../java/seedu/linkedout/commons/util/StringUtil.java
91.66% <80.00%> (-3.08%)
:arrow_down:

.../seedu/linkedout/logic/commands/SearchCommand.java
100.00% <0.00%> (ø)

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 233fca7...bdd5f1c. Read the comment docs.


Enable Apache Spark 2.0

This PR enables CaffeOnSpark to work with both Spark 1.x and Spark 2.x.
Once you provide appropriate SPARK_HOME, Spark 1.x/2.x could be built via "make build".

Issue #149 should be addressed.

CLA is valid!

+1


Add dispatch.yaml to route autojoin API requests to the autojoin service

It is always possible to use URLs constructed by App Engine, such as:

https://autojoin-dot-mlab-sandbox.appspot.com/autojoin/v0/node/list

However, App Engine also allows custom domains, such as:

https://autojoin.measurementlab.net/autojoin/v0/node/list

Like locate.measurementlab.net and the dispatch.yaml config for mlab-ns this PR adds a dispatch.yaml configuration for the production deployment of the autojoin API so autojoin.measurementlab.net can be the canonical API name.

This change is

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 98.918%

Totals

Change from base Build<PHONE_NUMBER>3:
0.0%

Covered Lines:
1189

Relevant Lines:
1202

💛  - Coveralls

Thank you!


[BUG] docker-compose up -d 出现问题 构建问题

Describe the bug
A clear and concise description of what the bug is.

运行 docker-compose up -d

Cloning into 'imagick'... fatal: unable to access 'https://github.com/Imagick/imagick/': Failed to connect to github.com port 443: Connection refused ERROR: Service 'webserver' failed to build: The command '/bin/sh -c cd /usr/local/src &&     git clone https://github.com/Imagick/imagick &&     cd imagick &&     git checkout ${IMAGICK_COMMIT} &&     phpize &&     ./configure &&     make &&     make install &&     cd .. &&     rm -rf imagick &&     docker-php-ext-enable imagick' returned a non-zero code: 128
which Branch / PHP Version are you using ?
php74
Steps to reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. MacOS, Linux, Ubuntu]
Browser [e.g. chrome, safari]
Docker Version:

docker -v
Docker version 19.03.5, build 633a0ea

Additional context
Add any other context about the problem here.

I'm not able to reproduce this issue. The php Container builds fine on my system. Please make sure you can reach github.


extract featture of the trained chinese model error: Attempting to use uninitialized value bert/encoder/layer_11/output/LayerNorm/beta

 53     def _create_graph(self):
 54         self._add_plh()
 55         self.vocab = tkz.load_vocab(FLAGS.vocab_file)
 56         mask = tf.cast(tf.sequence_mask(self._input_seq_len_plh), tf.int32)
 57         bert_config = modeling.BertConfig.from_json_file(FLAGS.bert_config_file)
 58         self._bert_model = modeling.BertModel(config = bert_config, is_training = False, input_ids = self._input_plh, input_mask = mask,
 59                                use_one_hot_embeddings = False)
 60         self._feas = self._bert_model.get_sequence_output()
 61         self._var_init = tf.global_variables_initializer()
 62         self.init_var()
 63     def init_var(self):
 64         tvars = tf.trainable_variables()
 65         initialized_variable_names = {}
 66         (assignment_map, initialized_variable_names) = modeling.get_assignment_map_from_checkpoint(tvars, FLAGS.init_checkpoint)
 67         tf.train.init_from_checkpoint(FLAGS.init_checkpoint, assignment_map)
 68     def extract_feas(self, db):
 69         sess = tf.Session(graph = self._graph)
 70         #with sess.graph.as_default():
 71         #    saver = tf.train.Saver()
 72         #    saver.restore(sess, 'data/bert/chinese_L-12_H-768_A-12/bert_model.ckpt')
 73         feas = []
 74         for batch in db.read_epoch(batch_size = 16, ctx_size = 1, num_thr = 1):
 75             batch = self.bert_batch(batch)
 76             fea = self.run(sess, batch, self._feas)
 77             feas.extend(list(fea))
 78             break
 79         return feas

Above the most related part of code which will raise below error, if I enable line 70-72, the error will gone, what is the problem?
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 1292, in _do_call
return fn(*args)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 1277, in _run_fn
options, feed_dict, fetch_list, target_list, run_metadata)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 1367, in _call_tf_sessionrun
run_metadata)
tensorflow.python.framework.errors_impl.FailedPreconditionError: Attempting to use uninitialized value bert/encoder/layer_11/output/LayerNorm/beta
[[{{node bert/encoder/layer_11/output/LayerNorm/beta/read}} = IdentityT=DT_FLOAT, _device="/job:localhost/replica:0/task:0/device:GPU:0"]]
[[{{node bert/encoder/Reshape_13/_25}} = _Recvclient_terminated=false, recv_device="/job:localhost/replica:0/task:0/device:CPU:0", send_device="/job:localhost/replica:0/task:0/device:GPU:0", send_device_incarnation=1, tensor_name="edge_1781_bert/encoder/Reshape_13", tensor_type=DT_FLOAT, _device="/job:localhost/replica:0/task:0/device:CPU:0"]]
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "extract_bert_feas.py", line 133, in
main()
File "extract_bert_feas.py", line 128, in main
train_feas = bert.extract_feas(train_db)
File "extract_bert_feas.py", line 76, in extract_feas
fea = self.run(sess, batch, self._feas)
File "/var/opt/git/bitbucket/nlp/gcws/src/models.py", line 47, in run
outputs = sess.run(nodes, feed)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 887, in run
run_metadata_ptr)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 1110, in _run
feed_dict_tensor, options, run_metadata)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 1286, in _do_run
run_metadata)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 1308, in _do_call
raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.FailedPreconditionError: Attempting to use uninitialized value bert/encoder/layer_11/output/LayerNorm/beta
[[{{node bert/encoder/layer_11/output/LayerNorm/beta/read}} = IdentityT=DT_FLOAT, _device="/job:localhost/replica:0/task:0/device:GPU:0"]]
[[{{node bert/encoder/Reshape_13/_25}} = _Recvclient_terminated=false, recv_device="/job:localhost/replica:0/task:0/device:CPU:0", send_device="/job:localhost/replica:0/task:0/device:GPU:0", send_device_incarnation=1, tensor_name="edge_1781_bert/encoder/Reshape_13", tensor_type=DT_FLOAT, _device="/job:localhost/replica:0/task:0/device:CPU:0"]]
Caused by op 'bert/encoder/layer_11/output/LayerNorm/beta/read', defined at:
File "extract_bert_feas.py", line 133, in
main()
File "extract_bert_feas.py", line 127, in main
bert.create_graph()
File "/var/opt/git/bitbucket/nlp/gcws/src/models.py", line 36, in create_graph
self._create_graph()
File "extract_bert_feas.py", line 59, in _create_graph
use_one_hot_embeddings = False)
File "/var/opt/git/bitbucket/nlp/gcws/src/bert/modeling.py", line 217, in init
do_return_all_layers=True)
File "/var/opt/git/bitbucket/nlp/gcws/src/bert/modeling.py", line 882, in transformer_model
layer_output = layer_norm(layer_output + attention_output)
File "/var/opt/git/bitbucket/nlp/gcws/src/bert/modeling.py", line 366, in layer_norm
inputs=input_tensor, begin_norm_axis=-1, begin_params_axis=-1, scope=name)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/contrib/framework/python/ops/arg_scope.py", line 182, in func_with_args
return func(*args, **current_args)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/contrib/layers/python/layers/layers.py", line 2299, in layer_norm
trainable=trainable)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/contrib/framework/python/ops/arg_scope.py", line 182, in func_with_args
return func(*args, **current_args)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/contrib/framework/python/ops/variables.py", line 350, in model_variable
aggregation=aggregation)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/contrib/framework/python/ops/arg_scope.py", line 182, in func_with_args
return func(*args, **current_args)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/contrib/framework/python/ops/variables.py", line 277, in variable
aggregation=aggregation)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/ops/variable_scope.py", line 1484, in get_variable
aggregation=aggregation)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/ops/variable_scope.py", line 1234, in get_variable
aggregation=aggregation)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/ops/variable_scope.py", line 538, in get_variable
aggregation=aggregation)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/ops/variable_scope.py", line 492, in _true_getter
aggregation=aggregation)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/ops/variable_scope.py", line 920, in _get_single_variable
aggregation=aggregation)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/ops/variables.py", line 145, in call
return cls._variable_call(*args, **kwargs)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/ops/variables.py", line 141, in _variable_call
aggregation=aggregation)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/ops/variables.py", line 120, in
previous_getter = lambda **kwargs: default_variable_creator(None, **kwargs)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/ops/variable_scope.py", line 2441, in default_variable_creator
expected_shape=expected_shape, import_scope=import_scope)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/ops/variables.py", line 147, in call
return super(VariableMetaclass, cls).call(*args, **kwargs)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/ops/variables.py", line 1104, in init
constraint=constraint)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/ops/variables.py", line 1266, in _init_from_args
self._snapshot = array_ops.identity(self._variable, name="read")
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/ops/array_ops.py", line 81, in identity
return gen_array_ops.identity(input, name=name)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/ops/gen_array_ops.py", line 3354, in identity
"Identity", input=input, name=name)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/framework/op_def_library.py", line 787, in _apply_op_helper
op_def=op_def)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/util/deprecation.py", line 488, in new_func
return func(*args, **kwargs)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/framework/ops.py", line 3272, in create_op
op_def=op_def)
File "/home/tom/pyenv/py3/lib/python3.5/site-packages/tensorflow/python/framework/ops.py", line 1768, in init
self._traceback = tf_stack.extract_stack()
FailedPreconditionError (see above for traceback): Attempting to use uninitialized value bert/encoder/layer_11/output/LayerNorm/beta
[[{{node bert/encoder/layer_11/output/LayerNorm/beta/read}} = IdentityT=DT_FLOAT, _device="/job:localhost/replica:0/task:0/device:GPU:0"]]
[[{{node bert/encoder/Reshape_13/_25}} = _Recvclient_terminated=false, recv_device="/job:localhost/replica:0/task:0/device:CPU:0", send_device="/job:localhost/replica:0/task:0/device:GPU:0", send_device_incarnation=1, tensor_name="edge_1781_bert/encoder/Reshape_13", tensor_type=DT_FLOAT, _device="/job:localhost/replica:0/task:0/device:CPU:0"]]

what is your tensorflow version

pip freeze|grep tensorflow
You are using pip version 18.0, however version 18.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
tensorflow-gpu==1.11.0
tensorflow-tensorboard==1.5.1

same problem. Did you figure it out?

same problem. Did you figure it out?
As I said

if I enable line 70-72, the error will gone,


Add an API

It'S best to add an API, so it can get implemented in other sites and not act as a standalone-project. As a bonus we can then put several frontends to it.

Api has been added and is published to master


Reset defaults/update Emulator launcher

I got the current SNES9x Emulator and then saw the LUA Autotrack script was tied to a 1.60 version. added in the older version, removed the newer one but now I crash everytime I try to start and can not figure out a reset to defaults/update emulator option.

By default, it uses the default application for roms that is set by your OS. You'll need to look up how to do that for your specific OS as I think it is slightly different between each version of Windows.
Alternatively, if you get the path to the specific version of snes9x-rr you have, you can set the exe as the launch application path in the randomizer settings.

Yeah I renamed the folder to the existing path as the exe was the same name.  Also yes updating my default program for windows worked as well.  Thank you.


Tracking Issue: Compile Sway to ACIR

Problem
Sway is another frontend by Fuel Labs that has the capabilities of being compiled to ACIR.
Solution
TBD
Alternatives considered
Additional context
(If applicable.)

This would be so cool to see. As the Alpha Swaylang user, I would love to be able to use that language for zk circuits too. That said, Noir feels very familiar coming from Sway.

We currently don't have much capacity to take this on, so I'll close until more interest is brought up for this


Bug: Code freeze on signin for windows

Describe the bug
When my code reaches the signin function it freezes, no response is returned.
Steps to reproduce
Run searreal DB with the following command
surreal start --log debug --user root --pass root memory

Write the following code in main.rs
use surrealdb_rs::param::Root;
use surrealdb_rs::protocol::Ws;
use surrealdb_rs::{Result, Surreal};

#[tokio::main]
async fn main() -> Result<()> {
    println!("sneaky");

    let client = Surreal::connect::<Ws>("localhost:8000").await?;

    println!("going dark");

    client
        .signin(Root {
            username: "root",
            password: "root",
        })
        .await?;

    println!("finish signing in");

    // Select a specific namespace and database
    client.use_ns("test").use_db("test").await?;

    println!("sat DB");

    Ok(())
}

The output from the surrealdb CLI is:
[2023-01-04 19:35:51] INFO  surreal::web <IP_ADDRESS>:59640 GET /rpc HTTP/1.1 101 "-" 679.6µs

The output from cargo run is:
   Compiling users_micservice v0.1.0 (F:\Programming\Rust\users_micservice)
    Finished dev [unoptimized + debuginfo] target(s) in 3.11s
     Running `target\debug\users_micservice.exe`
sneaky
going dark

If I forcibly stopped the CLI server using ctrl+c than the cargo run is also stop
Error: Error { kind: Socket, message: "socket error; receiving on a closed channel" }
error: process didn't exit successfully: `target\debug\users_micservice.exe` (exit code: 1)

My Cargo.toml
[package]
name = "users_micservice"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
tokio = { version = "1", features = ["full"] }
serde = "1.0.152"
serde_json = "1.0.91"
surrealdb-rs = { git = 'https://github.com/surrealdb/surrealdb.rs' }

Expected behaviour
to login normally
SurrealDB version
surreal 1.0.0-beta.8+20220930.c246533 for windows on x86_64
Contact Details
<EMAIL_ADDRESS>Is there an existing issue for this?

[X] I have searched the existing issues

Code of Conduct

[X] I agree to follow this project's Code of Conduct

This means you are using an unsupported version of the server. You need v1.0.0-beta.8+20221030.c12a1cc or newer. Also note that this repo is now deprecated. Please use https://github.com/surrealdb/surrealdb instead. The client is now located there.

Now that the Rust client library is being merged with the surrealdb crate itself, I am going to close this issue!


Enable fullgraph with torch.compile (v2)

What does this PR do?
Alternative implementation to #161
Closes #161
cc @borda @apaz-cli

Does this PR interfere with the decorator added in https://github.com/Lightning-AI/lightning-thunder/pull/48?

What do you mean by "interfere" precisely? I don't foresee people using both the torch.compile and TE engine executors together soon. But as long as we are not torch.compiling the TE autocast context manager it should be okay.


refactor: update unix build tags and add plan9

What does this PR do?
resolve obscure compile errors when trying to compile on different goos.
Use unix build tags and add plan9.
We can't implement uid/gid logic without breaks as plan9 uses strings while the api requires int.
Use plan9.Dup to redirect stderr.
See https://man2.aiju.de/2/dup
On plan9,

plan9.Dup(oldfd, newfd) == unix.Dup2(oldfd, newfd)
plan9.Dup(fd, -1) == unix.Dup(fd)

Why is it important?

!windows build tags is not true and causes misleading compile errors because it implies the file can be used in any goos other than windows while it's meant to be used for unix
_other has the same problem

Checklist

[ ] My code follows the style guidelines of this project
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added tests that prove my fix is effective or that my feature works

Author's Checklist

[ ]

Related issues

:hourglass_flowing_sand: Build in-progress, with failures

Buildkite Build
Commit: b4f6f1b1da5bd94fdbf3af333cf388d36edd0e5b

Failed CI Steps

:linux: Test Linux

:green_heart: Build Succeeded

Buildkite Build
Commit: 86c1607bb442e4d56fd8ff7295f58bd868e5e089

History

:broken_heart: Build #369 failed b4f6f1b1da5bd94fdbf3af333cf388d36edd0e5b


Fix sending emails with commas in their sender name.

To comply with RFC 5322 (https://www.rfc-editor.org/rfc/rfc5322#section-3.6.2) where commas in the from: field specify a list of multiple senders, we need to escape commas in the sender name. This is necessary if a project specifies its project name and therefore the sender name, e.g. as 'Coffee, and you?'.
Closes #1341.

yes, lets test outbound_spec

Thanks for the reminder! I added a regression test.


Add to cassandra-sink support json-unset

feat(cassandra-sink): Add to cassandra-sink support json-unset
Add support to "unset" JSON fields in prepared statements ( see https://issues.apache.org/jira/browse/CASSANDRA-11424 ).

This change is

@vlmiroshnikov Thanks!


Add YouTube video

YouTube URL (upload & processing should be done by 11:15pm ish): http://youtu.be/SJwnv3CgTGw
see http://www.schmutzie.com/weblog/how-to-embed-a-square-youtube-video-that-plays-in-an-infinite-loop for tips on square videos. (we don't want the infinite loop part)

Added


[WORKING] Vagrant provider

Liking create-env a lot over create env. It reduces the mental overhead when we go to add all of the subcommands, keeping it at one level seems really sane.

Yes,  and solves an import ambiguity issue.
Gonna rename this from vagrant to VirtualBox


Stale lastRenderedDerivedState

Context
Consider we have a store with a property called submitting and an action called setSubmitting.
Now imagine our UI, in a matter of a few milliseconds, dispatches setSubmitting(true), then it checks for errors in the form which causes immediately dispatching setSubmitting(false).
Problematic behavior
Apparently the current implementation of useMappedState shows the following behavior:

We start with lastRenderedDerivedState containing submitting: false. :heavy_check_mark:
checkForUpdates is called because we dispatched setSubmitting(true). :heavy_check_mark:
setDerivedState is invoked because lastRenderedDerivedState.current.submitting is false, but newDerivedState.submitting is true. :heavy_check_mark:
checkForUpdates is called because we dispatched setSubmitting(false). :heavy_check_mark:
setDerivedState is NOT INVOKED because, despite newDerivedState.submitting being false, lastRenderedDerivedState.current.submitting is also false (because it would only be updated after re-render and no re-render happened in this brief period). :x:

So at the end our component using useMappedState is only re-rendered once with submitting: true. The second render that would bring submitting: false doesn't happen.
Proposed solution
Don't wait until next re-render to update lastRenderedDerivedState. Simply update it right after setDerivedState is called. Also, change the name to lastDerivedState to make sense.

Could you please make a sandbox with a reproducing case? If I understand you correctly lastRenderedDerivedState.current.submitting should be true after setSubmitting(true) anyways.

Sure: https://codesandbox.io/s/0z6wz7qll

My proposed solution:
-    var lastRenderedDerivedState = useRef(derivedState);
-    // Set the last mapped state after rendering.
-    useEffect(function () {
-        lastRenderedDerivedState.current = derivedState;
-    });
+    var lastDerivedState = useRef(derivedState);

-            if (!shallowEqual(newDerivedState, lastRenderedDerivedState.current)) {
+            if (!shallowEqual(newDerivedState, lastDerivedState.current)) {
                 setDerivedState(newDerivedState);
+                lastDerivedState.current = newDerivedState;
             }

Thank you, now I get it. I think what you are suggesting is good.

I believe this may have issues with concurrent React. cc @sebmarkbage

The issue is reproducible with just plain state and can be simplified to:
const App = () => {
  const [state, setState] = React.useState(true);

  const prevState = React.useRef(state);
  React.useEffect(() => {
    prevState.current = state;
  });

  const wrappedSetState = value => {
    if (prevState.current !== value) {
      setState(value);
    }
  };

  return (
    <button
      onClick={() => {
        wrappedSetState(true);
        wrappedSetState(false);
      }}
    >
      Click me {JSON.stringify(state)}
    </button>
  );
};

Synchronous state updates are batched. As far as I know, there is a plan to make useState to bail out of update if state doesn't actually change so the example above will become redundant (no usePrevious would be needed). In the implementation of useMappedState in out codebase we use a patched version of useState that does not trigger an update if the state is unchanged and do not run a shallow equality check before calling setDerivedState. And this is sort of what @gustavopch is proposing I guess.

I've submitted https://github.com/facebookincubator/redux-react-hook/pull/24.


Update libc, unix bindings for FreeBSD

The libc and unix bindings for FreeBSD and Windows need to be updated to include C99 math entry points for the math library.

Linux x86.32 and x86.64 bindings have been updated thanks to @Blei

iOS bindings updated

Windows bindings updated. Only FreeBSD left to refresh

FreeBSD x86-32 updated by @chatur. Still need x86-64

FreeBSD x86-64 done; thanks again @chatur!


Cannot reproduce Performance Comparison. Re-render is occurred.

I'm sorry in continuous posting.
I read Performance Comparison section on docs. I tried reproducing this with version 3.8.6 many times, but could not do. Is there an example of this code?

shit... looks like I break the code with last published
patched with 3.8.7
https://codesandbox.io/s/priceless-williams-7btcl

@bluebill1049
Thank you for quick fix!


Font size units

Are font sizes passed to FillText/MeasureText in pixels or points?
If I use MeasureText it'll return the width, is the height of the text in pixels the font size?
edit: I've since checked the Web API and can see they've added bounding box ascent/descent measurements.

They should be in pixels at the moment. The web API also supports things like points, centimeters, inches and so on, but those depend on the monitor's DPI, and I'm not sure if or how that can be reliably determined.


Generate Log4jPlugins class does not compile in JPMS

Currently log4j-plugin-processor in version 3.0.0-beta3 of Log4j Core adds BND annotations to the generated code.
While these might be useful for OSGi users, they cause a compilation error if the biz.aQute.bnd.annotation module is not present:

On the compiler classpath,
A static dependency on the module is not declared in the module-info.java file.

A workaround for this issue is to add:
<dependency>
  <groupId>biz.aQute.bnd</groupId>
  <artifactId>biz.aQute.bnd.annotation</artifactId>
  <version>7.1.0</version>
  <scope>provided</scope>
</dependency>

to the compile-time only classpath and a:
requires static biz.aQute.bnd.annotation;

to the module descriptor. The annotations have a CLASS retention, so they don't cause problems at runtime.


Fix a hyperlink in Fall-ing for Finagle post

Double URL scheme.

Thanks @bdd, hope you're doing well!


Namespaced actors (Multitenant placement service)

Description
This PR implements support for namespaced actors (multi-tenant placement service).
Requirements

Multi-tenancy means that sidecars belonging to tenant A will not receive placement information for tenant B (As a consequence, multiple tenants can have actor types with the same name - a hotly requested feature).
When mTLS is enabled, the sidecar reported namespace should be verified through spiffe ID. When mTLS is not enabled, we accept the reported namespace as-is.

Some implementation details

The in-memory raft-based store was adapted to group placement data by namespace
Placement tables are kept per namespace
Sidecars in a namespace will only receive the placement table for their own namespace
A stream connection pool will be kept per namespace

Backwards compatibility scenarios:

The format of the placement table that the sidecars receive will not change, only its content will, making it fully backwards compatible.
Old sidecars that use TLS do report their namespace at the moment; we will default to that one, even if the sidecar didn’t report it explicitly (because it’s on an old version).
We have no way of knowing the namespace for old sidecars that do not use TLS. For these sidecars we will use a special “empty” namespace. When they connect to a new placement service, they will only get the actor types hosted on other old sidecars that are not on TLS (in the “empty namespace”).

TLS enabled
As soon as the placement server is updated, sidecars A, B and C will see each other’s actor types, and no others. The same is true for sidecars D, E and F.
TLS not enabled

Sidecars A and B will not have information about the actor types hosted on sidecar C.
Sidecar D will not have information about the actor types hosted on sidecar E and F.
Sidecars C, E and F will see each other’s actor-types, as before

For true backwards compatibility, we would keep sending actor types from all six sidecars to the old sidecars, but this is a security concern and breaks the first requirement for multi-tenancy above (”sidecars belonging to tenant A will not receive placement information for tenant B”). A malicious sidecar could connect with an older version on purpose and see actor types that belong to other namespaces.
This behaviour will be clearly documented (”If you’re not using TLS you need to have a uniform version per namespace, either upgrade all sidecars in a namespace or none.”).
Issue reference
https://github.com/dapr/dapr/issues/4711
https://github.com/dapr/dapr/issues/3167
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[X] Code compiles correctly
[X] Created/updated tests
[X] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

Linter is failing

Incredibly happy to see this land.

@holopin-bot @elena-kolevska Enjoy your Dapr badge!

Congrats on a great feature.


Typo in example code

Sample script is missing a dash in hyper-v-generation option in one of the last commented lines:
#If you're creating an OS disk, add the following: --os-type $osType -hyper-v-generation $hyperVGeneration

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

ID: abbee02a-d3f3-2032-f3f7-10ace7fdeca6
Version Independent ID: db7ee48d-7130-179a-e5b9-6eab8bf59e5f
Content: Create a managed disk from a VHD file in the same account - CLI sample - Azure Virtual Machines
Content Source: articles/virtual-machines/scripts/create-managed-disk-from-vhd.md
Service: azure-disk-storage
GitHub Login: @ramankumarlive
Microsoft Alias: ramankum

@vitalykorolev
Thanks for your feedback! We will investigate and update as appropriate.

Thanks for your contribution to our documentation
We are moving to a new user feedback system. As part of that effort, we are creating a content request in our backlog to address this gap and are closing this GitHub issue. The updated content will be published shortly.

Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
#please-close


Files cache refactoring

The files-cache has been using an emptyDir for it's underlying storage for ever.  Recently, it exhausted all the available resources on the app.ci cluster and caused an outage.  So, this PR is an overhaul of the files-cache:

Converting storage over to a 500Gb  PersistentVolume

Attaching the volume at /mnt
Cache will be located at /mnt/cache

Adding an InitContainer

Creates the /mnt/cache directory if it doesn't exist
Purges all content matching /mnt/cache/4.* upon restarts

Refactoring Python code

Drop support for Python 2 based logic
Update code to work under /mnt/cache
Cleaned up and streamlined logic

/hold
This update is going to require manual intervention to update the statefulsets.  The code will merge and deploy properly, but StatefulSets don't like you changing anything other than:
updates to statefulset spec for fields other than 'replicas', 'ordinals', 'template', 'updateStrategy', 'persistentVolumeClaimRetentionPolicy' and 'minReadySeconds' are forbidden

/lgtm

/close


nrf52_pca10040: get the erase block size from dts

Sample expect that to come from DTS, previously it was hardcoded in the
sample.
Signed-off-by: Anas Nashif<EMAIL_ADDRESS>

Codecov Report

Merging #9669 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #9669   +/-   ##
======================================
  Coverage    52.3%   52.3%
======================================
  Files         212     212
  Lines       25934   25934
  Branches     5589    5589
======================================
  Hits        13566   13566
  Misses      10122   10122
  Partials     2246    2246

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 bc6fb65...591de97. Read the comment docs.

I just wonder if the addition of the ble entry to supported should be done in a separate commit.

Agree


Span problem and Stack field problem.

Trying to use span option and what I see: If span is set up as 1, all works fine, but starts from 2 there is a problem on the right side of the table.

Also I have a Stack fields and looks like for this type of field package does not work.

Trying to use span option and what I see: If span is set up as 1, all works fine, but starts from 2 there is a problem on the right side of the table.

You need to ensure that there are two columns available ahead of the column you set as "span2." For example, if you set "span: 1" and it's the last column in the table, there won't be enough space for it to span. As a result, you'll end up with an extra column, which is what you see in the screenshot you shared.

Also I have a Stack fields and looks like for this type of field package does not work.

You can return an array and it will automatically wrapped in an stack field

I have 15 columns and extended column is second one with span set up as 10. But any number above 1 is making the same result on the right side. Higher number - bigger space in the right side.
Regarding Stack field - can you show any sample how to use it?

It works. But I have Stack field with two fields inside. And this Stack field ai would like to extend because the content I want to show - it should start in this place of index table.

Fixed here: v0.1.1

Thank you. Span works great. What about Stack field?

Using this approach Stack field is not extended.


useRouterMatch returns new object on each render

Basically reopening this issue https://github.com/ReactTraining/react-router/issues/7059

Please don't create duplicate issues.


[Feature]: Change the "to" prop of the Link component to "href"

What is the new or updated feature that you are suggesting?
Now: <Link to="overview">Overview</Link>
Proposal: <Link href="overview">Overview</Link>
Why should this feature be included?
 When developing a component library, for example, I have to specifically add the to prop to all of my components that may use a React Router Link, instead of a regular link. So I end up with something like this:

Why don't you guys change the to prop to href as a regular anchor tag or support both.
P.S. I am fully aware I can do a wrapper component to exchange the props, but I am more interested in the theory behind it.

You don't have to add to prop to all of your components. You just have to create your own wrapper over react-router's Link component. Like this:
import  { Link as ReactRouterLink } from 'react-router-dom'
import type { LinkProps as ReactRouterLinkProps } from 'react-router-dom'

type LinkProps = Omit<ReactRouterLinkProps, 'to'> & { href: string }

function Link(props: LinkProps) {
  const { href, ...linkProps } = props
  return <ReactRouterLink to={href} {...linkProps} />
}

A href is a very different thing than a to prop, hence the separate naming. The To type actually comes from history, and it can be either a string or an object: https://github.com/ReactTraining/history/blob/28c89f4091ae9e1b0001341ea60c629674e83627/packages/history/index.ts#L211
It doesn't represent a URL or path like href does, it represents a location in the router's history instance. If you're using a MemoryRouter, then it doesn't display that route state visibly at all. It also doesn't allow external links, which an href does.
Having a distinct prop resolves the points of confusion about how it functions. If you really want an href prop, do as @smashercosmo suggests above.

Thank you @timdorr for making it more clear to me now. Keep up the good work guys, really excited for an official release of V6


Remove dependency on go.uber.org/mock

https://github.com/search?q=repo%3Acontainerd%2Fnerdctl+go.uber.org%2Fmock&type=code
The tests that are using go.uber.org/mock should be rewritten to use plain structs and interfaces for simplicity.

we can use mockgen to generate mock interface implem and put then in seperate package. No need to redo the mockgen work.

we can use mockgen to generate mock interface implem and put then in seperate package. No need to redo the mockgen work.

We would still depend on go.uber.org/mock (during test runs) though, right?


DFP Updates

Linear Ticket:
SDK-1223
SDK-1224
Changes:

Updates the GetTelemetryID call to pass an object with the platform
Adds a top-level DFP object that exposes a getTelemetryId method that delegates to the existing DFPProvider

Notes:

Checklist:

[x] I have verified that this change works in the relevant demo app, or N/A
[x] I have added or updated any tests relevant to this change, or N/A
[x] I have updated any relevant README files for this change, or N/A

Well this is frustrating, the tests all pass in AS, but this one test is failing when run on CI/terminal 🤔


feat: Improved SSR caching and invalidation

Adds extension based content types along with cache headers setting for SSR sites.
The current issue is that invalidation is not correctly being detected so updated content is continuing to be stale on the server with the current cache headers.  Should content caching be reduced or should invalidation function be improved?
Related to #3389.

This PR has grown significantly based on the discovery of a few oddities in the implementation and feedback from other devs in the Discord channel.
Issue/oddities discovered:

The decision on whether or not to invalidate the CDN was based on changes to file names only. This means that changes to the contents of file which are not versioned would not cause cache invalidations. This is neither right or wrong, but not necessarily intuitive.
Non-versioned files are cached for a really long time by default but changes to the files didn't always cause invalidations and the TTL was so long that the cache wouldn't be expected to expire.
Content types of most files in the cache weren't set which meant that many pages served from cache had broken elements due to text encoding (like Emojis).
Attempts to correct the above issues via the fileOptions parameter meant that you were opting out of all default file metadata tagging in the cache and responsible for setting all metadata.

This PR attempts to resolve these oddities and make a more consistent experience for all SSR deployment types by adding an explicit cache attribute to the SsrSite props. The cache attribute allows specifying the textEncoding for text based content, as well as cache TTL for both versioned and nonversioned files. There are also options for overriding the default cache strategy with a full cache header for both versioned and nonversioned files. Independent of these props, the distribution will now attempt to add metadata for common web file types in the cache.
The largest change, and likely the most controversial, is the ability to change the invalidation strategy via the cache.cdnInvalidationStrategy prop. The default value of versioned will only check for changes to the files within the versioned file directory and will only invalidate those files as part of the deployment. The never and always options are both absolute values and fairly straight forward. The all option will perform a full invalidation based on the change of the content of any of the files in the cache.
Proposed changes to the SsrSite.props:
  cache?: {
    /**
     * Character encoding for text based assets stored in the S3 cache (ex: html, css, js, etc.). If "none" is specified, no charset will be returned in header.
     * @default utf-8
     * @example
     * ```js
     * cache: {
     *  textEncoding: "iso-8859-1"
     * }
     * ```
     */
    textEncoding?: "utf-8" | "iso-8859-1" | "ascii" | "none";
    /**
     * The strategy to use for invalidating the CDN cache. By default, the CDN cache will invalidate on changes any cached file, but this could become slow on very large projects.
     * - "never" - No invalidation will be performed.
     * - "all" - All files will be invalidated when any file changes. (Default, requires checking file content which will increase deployment time)
     * - "versioned" - Only versioned files will be invalidated when versioned files change.
     * - "always" - All files are invalidated on every deployment.
     * @default all
     * @example
     * ```js
     * cache: {
     *   cdnInvalidationStrategy: "versioned"
     * }
     * ```
     */
    cdnInvalidationStrategy?: "never" | "all" | "versioned" | "always";
    /**
     * The TTL for versioned files (ex: `main-1234.css`) in the CDN and browser cache. Ignored when `versionedFilesCacheHeader` is specified.
     * @default 1 year
     * @example
     * ```js
     * cache: {
     *  versionedFilesTTL: '30 days'
     * }
     * ```
     */
    versionedFilesTTL?: number | Duration;
    /**
     * The header to use for versioned files (ex: `main-1234.css`) in the CDN cache. When specified, the `versionedFilesTTL` option is ignored.
     * @default public,max-age=31536000,immutable
     * @example
     * ```js
     * cache: {
     *   versionedFilesCacheHeader: "public,max-age=31536000,immutable"
     * }
     * ```
     */
    versionedFilesCacheHeader?: string;
    /**
     * The TTL for non-versioned files (ex: `index.html`) in the CDN cache. Ignored when `nonVersionedFilesCacheHeader` is specified.
     * @default 1 day
     * @example
     * ```js
     * cache: {
     *  nonVersionedFilesTTL: '4 hours'
     * }
     * ```
     */
    nonVersionedFilesTTL?: number | Duration;
    /**
     * The header to use for non-versioned files (ex: `index.html`) in the CDN cache. When specified, the `nonVersionedFilesTTL` option is ignored.
     * @default public,max-age=0,s-maxage=86400,stale-while-revalidate=8640
     * @example
     * ```js
     * cache: {
     *   nonVersionedFilesCacheHeader: "public,max-age=0,no-cache"
     * }
     * ```
     */
    nonVersionedFilesCacheHeader?: string;
  };

The default configuration will assume that versioned content is desired to be long-lived (long TTL), and nonversioned content is desired to have fairly short CDN cache periods with hidden revalidation (aka stale while revalidated) and no user caching, with most deployments resulting in cache invalidation across the full site. This isn't the most "optimized" implementation, but as a default it offers the fewest pain-points since all changes should be visible immediately after deployment.

It's also worth mentioning the list of commonWebFileExtensions included in this PR in case there are strong opinions on this list or it's location.
const commonWebFileExtensions: Record<
  string,
  { mime: string; isText: boolean }
> = {
  txt: { mime: "text/plain", isText: true },
  htm: { mime: "text/html", isText: true },
  html: { mime: "text/html", isText: true },
  xhtml: { mime: "application/xhtml+xml", isText: true },
  css: { mime: "text/css", isText: true },
  js: { mime: "text/javascript", isText: true },
  mjs: { mime: "text/javascript", isText: true },
  apng: { mime: "image/apng", isText: false },
  avif: { mime: "image/avif", isText: false },
  gif: { mime: "image/gif", isText: false },
  jpeg: { mime: "image/jpeg", isText: false },
  jpg: { mime: "image/jpeg", isText: false },
  png: { mime: "image/png", isText: false },
  svg: { mime: "image/svg+xml", isText: true },
  bmp: { mime: "image/bmp", isText: false },
  tiff: { mime: "image/tiff", isText: false },
  webp: { mime: "image/webp", isText: false },
  ico: { mime: "image/vnd.microsoft.icon", isText: false },
  eot: { mime: "application/vnd.ms-fontobject", isText: false },
  ttf: { mime: "font/ttf", isText: false },
  otf: { mime: "font/otf", isText: false },
  woff: { mime: "font/woff", isText: false },
  woff2: { mime: "font/woff2", isText: false },
  json: { mime: "application/json", isText: true },
  jsonld: { mime: "application/ld+json", isText: true },
  xml: { mime: "application/xml", isText: true },
  pdf: { mime: "application/pdf", isText: false },
  zip: { mime: "application/zip", isText: false },
};

Another change introduced by this PR is the shift from exclude and include as properties on the fileOptions to a shared filters array which allows for the exclude and include filters to be applied in different orders to allow more specific targeting of files.
Previous file options:
const fileOptions = [
  {
    exclude: "*",
    include: "*.html",
    cacheControl: "max-age=0,no-cache,no-store,must-revalidate",
  },
  {
    exclude: "*",
    include: ["*.js", "*.css"],
    cacheControl: "max-age=31536000,public,immutable",
  },
];

New file options:
const fileOptions = [
  {
    filters: [{ exclude: "*" }, { include: "*.html" }],
    cacheControl: "max-age=0,no-cache,no-store,must-revalidate",
  },
  {
    filters: [{ exclude: "*" }, { include: "*.js" }, { include: "*.css" }],
    cacheControl: "max-age=31536000,public,immutable",
  },
];

The advantage to this approach is that it allows filters to be specified in the manner that they will be applied in S3 (ref: Use of Exclude and Include Filters).
Previously, it was impossible very hard to apply a file option to all extensions in site while excluding a subset that were in a directory because all the exclude filters were applied first, followed by the include. With this new structure, the order can be specified to allow this sort of filtering.
const fileOptions = [
  {
    filters: [
      { exclude: "*" },
      { include: "*.csv" },
      { exclude: "public/*" },
    ],
    cacheControl: "private,max-age=0,no-cache,no-store",
  }
];

@bayssmekanique made a few cosmetic changes along the way while learning the code.
Appreciate the detailed comments. Lemme know when it's ready to merge!

Thanks @fwang. I made one reversion. The if/else logic in the invalidation digest section would result in only the versioned files being fed into the hash, when it should really be both in the case of an all invalidation strategy.
Ref: https://github.com/sst/sst/blob/10ce93795e4aabef7366570c8bce788895d164f9/packages/sst/src/constructs/SsrSite.ts#L1506-L1532
Everything else looks good. Ready to merge.

if this can make it into a (snapshot?) release tonight i'd love to play with it tomorrow! cc @fwang

if this can make it into a (snapshot?) release tonight i'd love to play with it tomorrow! cc @fwang

<EMAIL_ADDRESS>

fyi, i've had some other priorities shifting my attention and won't get back to this for a couple weeks :/

@fwang, doesn't sound like @adamelmore will be able to QA this PR anytime soon. Can we merge for the next minor release?


feat(storage): add current_epoch to support decoupling

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
Add current_epoch to support decouple. We will save two epochs (committed_epoch and current_epoch), We will commit an epoch with a checkpoint, and update committed_epoch. And we will just update current_epoch without a checkpoint.
Get_epoch, Flush, and Pin_snapshot will return committed_epoch and current_epoch. Our batch can pick the right epoch for the query.
Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Documentation
If your pull request contains user-facing changes, please specify the types of the changes, and create a release note. Otherwise, please feel free to remove this section.
Types of user-facing changes
Please keep the types that apply to your changes, and remove those that do not apply.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note
Please create a release note for your changes. In the release note, focus on the impact on users, and mention the environment or conditions where the impact may occur.
Refer to a related PR or issue link (optional)

Pin_snapshot will return committed_epoch and current_epoch.

The snapshot of which epoch is pinned in fact? Do we also need to specify these 2 epochs for unpinning?

Pin_snapshot will return committed_epoch and current_epoch.

The snapshot of which epoch is pinned in fact? Do we also need to specify these 2 epochs for unpinning?

pinned committed_epoch, because current_epoch always ge committed_epoch.

Pin_snapshot will return committed_epoch and current_epoch.

The snapshot of which epoch is pinned in fact? Do we also need to specify these 2 epochs for unpinning?

we also pin snapshot with committed_epoch, only return two epochs for a query (current >= committed). So we will unpin snapshot with committed_epoch.

Pin_snapshot will return committed_epoch and current_epoch.

The snapshot of which epoch is pinned in fact? Do we also need to specify these 2 epochs for unpinning?

we also pin snapshot with committed_epoch, only return two epochs for a query (current >= committed). So we will unpin snapshot with committed_epoch.

It would be better if we were able to specify which type of epoch we want to pin? So that there's no need to unpin the unused one.

e2e test failed.


Is this typo?

phpcs.xml line 136
<file->tests</file->

Instead of
<file>tests</file>

Nice catch, yes indeed it is!

Nice catch, yes indeed it is!

have you fixed it?

have you fixed it?


Api kubernetes watch for listing node names

let's merge to sprint3 branch instead of styling
I'm closing this without merging and opening a new PR


Fixes #172

New messages being pushed to the phone weren't appearing at the bottom of the feed; this fixes that issue.

Automated message from Dropbox CLA bot
@niftynei, it looks like you've already signed the Dropbox CLA. Thanks!


Settings

Following https://github.com/jtauber/pyuca/pull/17#issuecomment-338447484
this PR rebases the settings branch on master
including settings normalization and strength (each with unit tests)
and keeping out backwards - for lack of tests.

@lucafavatella thank you! I will get to all this later in the week


Ignore TLS/SSL-Certificate for ex. Matrix

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
Other
🔖 Feature description
Add for some services, like Matrix/Synapse, a "ignore TLS/SSL-Certificate" Checkbox
✔ Solution
See: https://github.com/louislam/uptime-kuma/issues/1904
We cant send messages from uptime-kuma to our selfhosted, maybe localhost, Matrix-Synpase-Server.
Just add a Ignore TLS/SSL-Certificate (or a "--insecure"-Tag), when you check:
curl -XPOST -d --insecure '{"type": "m.login.password", "identifier": {"user": "botusername", "type": "m.id.user"}, "password": "passwordforuser"}' "https://home.server/_matrix/client/r0/login"

Its work, but just with the Tag "--insecure"

❓ Alternatives
No response
📝 Additional Context

I have same problem with Matrix. Please check that.

Closing as https://github.com/louislam/uptime-kuma/labels/wontfix.
Doing so (ignoring certs for notifications) could mean that an attacker intercepts these notifiations as they are no longer as MITM attacks are possible in this case.
Users seeking this should either

register the CA for the self-signed cert used by the $Notificationprovider server you host with uptime-kuma
or provide said $Notificationprovider server with a valid cert (letsencrypt/...)

Notifications are very different from monitors, where this is handy.
For notifications, you don't want them going to a potentially different server.


Reset tracker without clearing cache

It would be awesome if like the actual product, clicking and holding the Jan 1 (or Dec 31, can't remember which one) button would flash all the buttons and reset all the dates, instead of having to clear browser cache.

That would be a nice feature. PRs are welcome.


Skip apply cookies if there isn't incapsula script available

The title explains the change itself

I've found this to be useful and work.
How about merging it?


Transparency doesnt work with wgpu backend

Seems transparency does not work on wgpu, is this normal ?
I would happily use glow, but fonts are a bit aliased. Is there a workaround this ?

features = ["wgpu", "default_system_font", "debug", "palette" ]

features = ["glow", "glow_default_system_font", "debug", "palette" ]

See https://github.com/hecrj/iced/pull/371 / https://github.com/gfx-rs/wgpu/issues/687
tl;dr for now wgpu hardcodes opaque mode, so it needs to be patched. You can use my fork:
[patch.crates-io]
# patch: transparency (config.composite_alpha_mode = hal::window::CompositeAlphaMode::PREMULTIPLIED)
wgpu-core  = { git = "https://github.com/myfreeweb/wgpu", branch = "v0.6-alpha" }
wgpu-types = { git = "https://github.com/myfreeweb/wgpu", branch = "v0.6-alpha" }

See #371 / gfx-rs/wgpu#687
tl;dr for now wgpu hardcodes opaque mode, so it needs to be patched. You can use my fork:
[patch.crates-io]
# patch: transparency (config.composite_alpha_mode = hal::window::CompositeAlphaMode::PREMULTIPLIED)
wgpu-core  = { git = "https://github.com/myfreeweb/wgpu", branch = "v0.6-alpha" }
wgpu-types = { git = "https://github.com/myfreeweb/wgpu", branch = "v0.6-alpha" }

I've followed this & used your fork, modified the examples, but the transparency still seems not working on macOS 11.0.1 Big Sur:
diff --git a/Cargo.toml b/Cargo.toml
index 6221ae4..6bbfb22 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -100,3 +100,8 @@ iced_web = { version = "0.3", path = "web" }
 [package.metadata.docs.rs]
 rustdoc-args = ["--cfg", "docsrs"]
 features = ["image", "svg", "canvas"]
+
+[patch.crates-io]
+# patch: transparency (config.composite_alpha_mode = hal::window::CompositeAlphaMode::PREMULTIPLIED)
+wgpu-core  = { git = "https://github.com/myfreeweb/wgpu", branch = "v0.6-alpha" }
+wgpu-types = { git = "https://github.com/myfreeweb/wgpu", branch = "v0.6-alpha" }
\ No newline at end of file
diff --git a/examples/clock/Cargo.toml b/examples/clock/Cargo.toml
index c6e3237..b2a819a 100644
--- a/examples/clock/Cargo.toml
+++ b/examples/clock/Cargo.toml
@@ -7,4 +7,4 @@ publish = false

 [dependencies]
 iced = { path = "../..", features = ["canvas", "tokio", "debug"] }
-chrono = "0.4"
+chrono = "0.4"
\ No newline at end of file
diff --git a/examples/clock/src/main.rs b/examples/clock/src/main.rs
index b317ac0..3a52ff2 100644
--- a/examples/clock/src/main.rs
+++ b/examples/clock/src/main.rs
@@ -1,3 +1,5 @@
+mod style;
+
 use iced::{
     canvas::{self, Cache, Canvas, Cursor, Geometry, LineCap, Path, Stroke},
     executor, time, Application, Color, Command, Container, Element, Length,
@@ -6,6 +8,11 @@ use iced::{

 pub fn main() -> iced::Result {
     Clock::run(Settings {
+	window: iced::window::Settings{
+	    decorations: false,
+	    transparent: true,
+	    ..iced::window::Settings::default()
+	},
         antialiasing: true,
         ..Settings::default()
     })
@@ -32,7 +39,7 @@ impl Application for Clock {
                 now: chrono::Local::now(),
                 clock: Default::default(),
             },
-            Command::none(),
+            Command::none()
         )
     }

@@ -55,6 +62,10 @@ impl Application for Clock {
         Command::none()
     }

+    fn background_color(&self) -> Color {
+	Color::TRANSPARENT
+    }
+
     fn subscription(&self) -> Subscription<Message> {
         time::every(std::time::Duration::from_millis(500))
             .map(|_| Message::Tick(chrono::Local::now()))
@@ -71,6 +82,7 @@ impl Application for Clock {
             .padding(20)
             .center_x()
             .center_y()
+	    //.style(style::Container)
             .into()
     }
 }
@@ -82,7 +94,6 @@ impl canvas::Program<Message> for Clock {
         let clock = self.clock.draw(bounds.size(), |frame| {
             let center = frame.center();
             let radius = frame.width().min(frame.height()) / 2.0;
-
             let background = Path::circle(center, radius);
             frame.fill(&background, Color::from_rgb8(0x12, 0x93, 0xD8));

But switching to glow works:
diff --git a/examples/clock/Cargo.toml b/examples/clock/Cargo.toml
index c6e3237..fce87f2 100644
--- a/examples/clock/Cargo.toml
+++ b/examples/clock/Cargo.toml
@@ -6,5 +6,5 @@ edition = "2018"
 publish = false

 [dependencies]
-iced = { path = "../..", features = ["canvas", "tokio", "debug"] }
-chrono = "0.4"
+iced = { path = "../..", features = ["glow", "glow_canvas", "tokio", "debug"] }
+chrono = "0.4"

Is this still an issue in the latest versions of wgpu?

Yes, you can see that https://github.com/gfx-rs/wgpu/issues/687 is still open. I still use a forked wgpu with a one-line patch for this.

I'm still having this same issue on macOS with the latest iced and wgpu, although it looks like wgpu merged that PR. Any advice on a fix / workaround?
Thanks!

I believe I'm hitting this as well - here is a small sample project:

https://github.com/leoshimo/commandbar_iced/blob/main/src/main.rs

I've set application + children to have transparent background, but seeing a black box being rendered:

Just another data point, on my system transparency works for WGPU_BACKEND=gl but not WGPU_BACKEND=vulkan.

It seems the linked PR has been closed, so perhaps a fix can be merged ?

Hi!
Transparency isn't supported on the WebGL backend. Does it make sense to open this as a separate issue?