Feature clockformat

I tried to implement my feature request issue https://github.com/mariovisic/garmin_edge_active_data_field/issues/1#issue-926734811
Please note however that I've not written any Monkey C before and do not have a Garmin IQ build environment. So it may be best to think of this as pseudo code!
In the past I attempted to set up a build environment but I work on Linux and it seems that Linux support for the SDK is very outdated.

I was able to install version 3.2.3 of the SDK. So, I can at least confirm that it compiles now. I couldn't test it in the simulator because the connectiq exectuable on Linux has some ancient runtime dependencies that I can't (and don't really want to) install.

Closing this.I found how to use the system setting for 12/24 hour format. Now working on a branch to use that.

Thanks for putting the time in to implement this, sorry again that I missed this earlier


Update Production

Please read the Pull Request Checklist to ensure you have everything that is needed to get your contribution merged.

Pull Request Test Coverage Report for Build 338

243 of 395 (61.52%)  changed or added relevant lines in 35 files are covered.
23 unchanged lines in 7 files lost coverage.
Overall coverage increased (+0.1%) to 44.908%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

frappe/init.py
5
6
83.33%

frappe/core/doctype/report/test_report.py
11
12
91.67%

frappe/desk/doctype/kanban_board/kanban_board.py
0
1
0.0%

frappe/desk/form/linked_with.py
0
1
0.0%

frappe/desk/query_report.py
0
1
0.0%

frappe/website/context.py
0
1
0.0%

frappe/www/login.py
1
2
50.0%

frappe/utils/data.py
3
5
60.0%

frappe/website/render.py
0
2
0.0%

frappe/www/list.py
1
3
33.33%

Files with Coverage Reduction
New Missed Lines
%

frappe/desk/doctype/kanban_board/kanban_board.py
1
20.49%

frappe/desk/form/linked_with.py
1
77.97%

frappe/permissions.py
1
71.48%

frappe/chat/doctype/chat_message/chat_message.py
1
23.36%

frappe/utils/bot.py
1
79.58%

frappe/www/login.py
1
57.38%

frappe/tests/test_naming.py
17
70.69%

Totals

Change from base Build 310:
0.1%

Covered Lines:
17375

Relevant Lines:
38690

💛  - Coveralls


Testcase group by namespace in VS shows some testcases in "External" namespace

Description

"External " namespace appearing for testcases which have no source info

Steps to reproduce

Open Testplatform.sln in VS
Group by namespace in testwindow

Expected behavior

Should be group by proper namespace.

Actual behavior

Some testcases group by namespace External.

@smadala as of the most recent commit I'm seeing this with the Foundatio.Azure.Tests project (https://github.com/exceptionless/foundatio)

@niemyjski https://github.com/Microsoft/vstest/issues/373 will fix this scenario. please use workaround for temporary fix.
<PropertyGroup>
    <DebugType Condition="'$(TargetFramework)' != '' AND !$(TargetFramework.StartsWith('netcoreapp'))">Full</DebugType>
</PropertyGroup>

Will this be fixed in RC5 / RTM? I'd rather not update my project file if this will be fixed soon.

Currently not in RTM list. @sbaid @codito.

That is sad to hear, I'd think this use case is quite common.

@niemyjski fixed this in Microsoft.NET.Test.Sdk: 15.0.0-preview-20170222-09


Feature/request and authentication improvements

Fix: #1
Fix: #2

added retries and timeout settings
maintenance will now retry requests up to IBEAM_REQUEST_RETRIES (default 1)
refactored tickle/validate logic
now uses tickle to verify authentication and extend sessions, instead of validate
now checks for authentication status apart from successful requests
deprecated -l/--validate standalone argument

Original author confirmed the issues have been fixed. Going ahead with a merge.


Answer gets significantly wrong when input is long

When I apply the following code on long articles
from bootleg.end2end.bootleg_annotator import BootlegAnnotator
ann = BootlegAnnotator()
result = ann.label_mentions(text)

The results significantly get worse when the article is longer. Is it expected?
You may use the below text to test:
And yet, 100 years from now, Obama’s presidency will be hailed as the most transformative of our lifetimes, and Donald Trump’s will be viewed with the same scorn that followed the Dred Scott decision. Like that pre-Civil War Supreme Court case, Trump will forever be condemned as a racial reprobate whose words and actions inspired white supremacists and neo-Nazis.\nLast week’s slaughter of Muslims in New Zealand was allegedly committed by a fascist who claimed to draw inspiration from President Trump, among others. It was the latest in a long line of tragedies that our president failed to clearly condemn. After the 2017 riots in Charlottesville, Trump proclaimed a moral equivalence between neo-Nazis and their opponents. Following the killings in Christchurch, the president dismissed the threat of white supremacy while claiming the rising tide of violence coming from the far right was limited to a few troublemakers with “very serious problems.”\nTrump’s acting chief of staff appeared on national television to declare that “the president is not a white supremacist.” White House counselor Kellyanne Conway once again shamed herself by dismissing the fascist mass murderer from Australia as an “eco-terrorist.” The president’s apologists denied that the current commander in chief was inspiring right-wing violence. But the Center for Strategic and International Studies reported in November that far-right attacks rose in Europe by 43 percent since 2016, while right-wing terrorist attacks have quadrupled in the United States over the same time. Hate crimes rose 17 percent in 2017.\nThis troubling chapter in U.S. history has one author — and his name is Donald Trump. This sputtering reality star has created a political identity and corrupt presidency inspired by the wave of racism that followed Obama’s. The Manhattan multimillionaire’s 2016 calls for a Muslim ban and creation of a Muslim registry; the claim of ignorance toward former Ku Klux Klan leader David Duke; the attack on a Hispanic judge’s integrity; the callousness shown toward a Muslim Gold Star family; and the anti-Semitic tweet featuring a Star of David and piles of $100 bills next to Hillary Clinton’s face. These are just a few of the racially charged offenses that Trump committed even before Americans elected him president.\nThe shocking conclusion to the 2016 campaign made millions of Americans, including me, look foolish for believing that Obama’s victories in 2008 and 2012 had proved that the United States had emerged from the scourge of racism infecting it for more than four centuries. I remain shocked that this strain of bigotry still fuels the political careers of Trump and his enablers on Capitol Hill.\nThe Rev. Martin Luther King Jr. often said that “the arc of the moral universe is long, but it bends toward justice.” That is but one reason why the rise in bigotry shown to Muslims, Jews, Hispanics, blacks and “others” has been so discouraging in the age of Trump. Like those who believed these racists were relics from a bygone age, I had also convinced myself that my Republican colleagues were so repelled by racism that they would never support a leader who provided inspiration to neo-Nazis and white supremacists; the manifesto of the New Zealand killer and the words of David Duke after Charlottesville showed just how wrong I was.\nThat’s why any policy differences I had with Obama now seem so insignificant. Americans who still have faith in the upward arc of King’s moral universe should be grateful for Obama’s presidency and the way his election exposed the white racism that is still at large in our land. If changing the Constitution and reelecting Obama two more times would break the fever that now ravages Trump’s Washington, I would cheerfully champion the passage of that constitutional amendment, slap a “Hope and Change” sticker on my shirt, and race to the nearest voting booth to support the man historians will remember as the most significant president since Abraham Lincoln.\nRead more:

Thank you for letting me know and for providing an input. Let me poke around and see. Bootleg was trained on individual sentences --- geared more towards short text NED like for QA. So it might be worth trying to take the document and split in to sentences (nltk has a sentence splitter you can try here). I'll test and see. This is great feedback!

@lorr1 Thank you for your answer! Yes, I currently use nltk to split the doc into sentences as a workaround. Not sure if there exists such a dataset, but maybe if the model would be able to take in long documents, the extra context might also benefit the performance? Just some random idea haha


[Enhancement] Show homebridge instance name

Currently the web page always shows "Homebridge" as the title. It would be nice if it could use the actual name given for the homebridge instance.
Background: I have multiple homebridge servers running and when you have multiple web pages open it can become cumbersome to see which servers page you're on.
Thanks for this awesome software!

Hi @normen,
Thanks for your suggestion. This will be added in the next major release.

Awesome, thanks. For now the nice "theme" feature helps - but not in the tab bar :)

Thanks for your work. But it would be great if the instance name were beside the status button. When I'm connect on my smartphone I don't have the page name on the tab bar.


stateful components should have easily manipulable internal state🔥

Is your feature request related to a problem? Please describe. 🤔
Component manipulation is limited. If components are objects, the meaning of the component tag should be to place any component into the document, no matter how it is produced or identified. One can declare a component that modifies its own state by referencing itself.
   component HelloWorld:
    y : int = 17

    `template`:
      tDiv:
        "Hello, world {self.y}!"
      tButton:
        "change world"
        @click:
          self.y += 1

However, one cannot even bind a component to an identifier and then add it to the document by the identifier. If we say
  var hw = initHelloWorld("hw", y=88)
then
hw will fail to render anything, and 'component hw' will fail because the renderer currently assumes that we need to initialize a new component whenever we use the component tag.
Describe the solution you'd like 💡

component hw should render to the document in the same way  component HelloWorld(y=88) would.

In line with the goal of having methods and other things that modify component fields, any other changes required for the normal features of object declaration and field access to work should be implemented. I note, for example that one cannot declare exported fields with *

Describe alternatives you've considered 💁♀
Since text gets rendered just by placing the text node, it might be argued that the component tag should not exist at all and that the macro should just render any statement that results in a component in the same way. However I don't think its likely to be worth the change in the documented API
One can wrap components in some other datatype that houses the state which can be publicly modified, but this would be a needless addition of a new type that the programmer needs to juggle. stateful components are the only datatype that the programmer will really want to deal with.

How about
component MyComponent:
  ....

...

var myComp = useComponent(MyComponent)

...

buildHtml:
  component MyComponent
  component myComp

This will available in new HappyX version

I think that this is better way
var myComp = use component MyComponent

buildHtml:
  component MyComponent
  component myComp

This also will work with
var myPathParam = use pathParam arg

"/some/<myPathParam>"

I think that this is better

Sounds good! If the syntax of 'use' there were flexible enough to allow for a singleton component to render in many places, that might be even better. I think it would be only marginally more useful to the programmer, though, so may not be worth the effort.
Question: how would you intend to initialize components.? Currently MyComponent acts as a proc in the DSL and is initialized as MyComponent(myVal=0), but in the global environment of nim MyComponent (<stuff>) is a constructor and requires :, so outside the buildHtml environment, it looks like we can currently only go
var myComp = MyComponent(myVal : 0)
or
var myComp = initMyComponent("required identifying string", myVal = 0)
I assume use will be some kind of macro that allows us to use the normal syntax of the component tag, like
var myComp = use component MyComponent(myVal = 0)?
If that is so it looks like initMyComponent(), if it persists internally, should be made private if possible. It seems like the intent of the library is rapidly becoming that users of the library should never have to  call this function.

I assume use will be some kind of macro that allows us to use the normal syntax of the component tag, like
var myComp = use component MyComponent(myVal = 0)?

Yeap, you're right 🙂

If that is so it looks like initMyComponent(), if it persists internally, should be made private if possible. It seems like the intent of the library is rapidly becoming that users of the library should never have to call this function.

Nope, it impossible, because all component use it in buildHtml

Only this usage is allowed

Because it translates into:

var myComp = use(component Button):
  "This is button in component"

So
var myComp = use component MyComponent(myParam=3):
  "this text is a field of the component?"

should translate to
var myComp = use(component MyComponent(MyParam=3)):
  "this text is a field of the component?"

I ask because in a buildHtml environment, eventually stuff in a block form gets interpreted as a child tag in the html document. For instance, coming from Karax, MyParam is an argument to the proc, while the text would be interpreted as a child VNode. There, it makes it hard to use other 'body' macros inside the DSL and leads to a syntactic difference between using a macro or proc inside the DSL vs in global scope.

I mean that syntax
var x = use component Comp(...):
  ...

is impossible, because Nim translates it into
var x = use(component Comp(...)):
  ...

Solution is
# this
var x = use(component Comp(...):
  ...
)
# or this
var y = use:
  component Comp(...):
    ...

Upd usage syntax for variables:
buildHtml:
  component Component(...)
  component `comp`

here is usage example

And here result

Final version:

P.S.:
Button.action is State[proc(): void]

Solved in https://github.com/HapticX/happyx/commit/02f65ccb913e4523595d57e1d2b3867a6114c427

Ah, subtle! I think this is what I was trying to get at. The programmer can want either the 'wrong' or 'right' translation depending on the situation, it seems, but it's certainly good to know which one you are going to get!

is impossible, because Nim translates it into
var x = use(component Comp(...)):
  ...

Solution is
# this
var x = use(component Comp(...):
  ...
)


remove recursion in optimizer rules

Which issue does this PR close?

Closes #.
Rationale for this change
Remove recursion in optimizer rules. and utilize the optimizer traverse the plan tree.

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

Rely on #4618

Marking as draft as it builds on https://github.com/apache/arrow-datafusion/pull/4618

If possible I think it would be worth the time trying to avoid making Filter fields pub as we have discussed earlier. I left a suggestion on how maybe that could be done.

I find a good way to resolve it by adding #[non_exhaustive]

I find a good way to resolve it by adding #[non_exhaustive]

This is reasonable (it will prevent construction outside of the crate, so in datafusion core and planner) 👍  nice


ENH: allow matching of general bipartite graphs

This provides a Cython implementation of the Hopcroft--Karp algorithm for solving the maximum matching problem for bipartite graphs.
Context and motivation
SciPy currently implements a solver for maximum bipartite matching in scipy.sparse.csgraph.maximum_bipartite_matching. However, the main interest in this one appears to have been in reordering rows/columns of sparse matrices, and the function makes the assumptions that the partitions in the input graph have equal cardinality and that a perfect matching exists; as such, not much maximization is actually going on and all the algorithm does is find a feasible solution. Now, there's nothing wrong with that, but it's likely not what you might expect coming to a method called maximum_bipartite_matching from a graph theory context.
This PR ties in with the discussion towards the end of #10296 in which the topic was including a version of scipy.optimize.linear_sum_assignment that takes advantage of sparsity; although this is a separate problem, before moving to that it seemed to make more sense to deal with the more fundamental problem of finding a maximum matching. It also follows the spirit of #10566 and provides an implementation of a well-known algorithm that's easy to understand and thus hopefully maintain, with an eye towards performance so that we improve on the existing implementation for the cases where they overlap, and with large improvements over pure Python implementations such as the one in NetworkX.
The algorithm revolves around the notion of augmenting paths, which matches the approaches in scipy.optimize.linear_sum_assignment and the proposed scipy.sparse.csgraph.maximum_flow; this isn't a huge benefit in and of itself, but it does mean that being able to read one makes it easier to read the others. As such, a reviewer with a surplus of time going through this might also want to take a look at #10566.
In the process, we also fix an issue with the old documentation: Here, the main concern was permuting the rows/columns of a matrix to make its diagonal zero-free, but in case the input matrix contained explicit zeros in its sparse representation, the diagonal would in fact as well; we fix this by turning the bug into a feature and explicitly interpreting explicit zeros as edges in the bipartite graph. We keep the original motivation as an example in the xmldoc of the revised function.
Correctness
In addition to the included unit tests, we've run checks against the corresponding function in NetworkX, checking that the cardinalities of a maximum matching agree for random inputs, e.g.:
from random import randint, random
for _ in range(100):
    n = randint(100, 1000)
    m = randint(100, 1000)
    density = random()
    graph = scipy.sparse.rand(n, m, density=density, format='csr')
    G = nx.algorithms.bipartite.from_biadjacency_matrix(graph)
    assert 2 * np.sum(maximum_bipartite_matching(graph, perm_type='column') >= 0) ==\
        len(nx.algorithms.bipartite.maximum_matching(G, top_nodes=range(n)))

This clearly does not prove correctness in any way, but it does at least provide some confidence that it's working.
Performance
Using the same random matrices as above we can provide a rough benchmark of our approach against the existing implementation and the one available in NetworkX. How well it performs will depend on characteristics of the input, but we do at least seem to be gaining a good amount of performance in addition to solving a much more general problem:
n = 5000
density = .1
graph = scipy.sparse.rand(n, n, density=density, format='csr', random_state=42)
G = nx.algorithms.bipartite.from_biadjacency_matrix(graph)

>>> %timeit maximum_bipartite_matching(graph, perm_type='column')
8.95 ms ± 183 µs per loop (mean ± std. dev. of 7 runs, 100 loops each)
>>> %timeit old_maximum_bipartite_matching(graph, perm_type='column')
141 ms ± 8.52 ms per loop (mean ± std. dev. of 7 runs, 10 loops each)
>>> %timeit nx.algorithms.bipartite.maximum_matching(G, top_nodes=range(n))
2.01 s ± 118 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)

Marking this as WIP just to get a chance to look at the CI output, including the documentation this builds.

This looks good, let's try to get it in for 1.4.0.
There's a small merge conflict, could you rebase @fuglede?

Thanks @rgommers, merged and rebased.
Here's a possible release note entry:

scipy.sparse.csgraph.maximum_bipartite_matching now allows non-square inputs, no longer requires a perfect matching to exist, and has improved performance.

CI failure is unrelated:
=================================== FAILURES ===================================

 build/testenv/lib/python3.6/site-packages/scipy/optimize/tests/test__differential_evolution.py

[gw1] linux -- Python 3.6.7 /home/travis/virtualenv/python3.6.7/bin/python

worker 'gw1' crashed while running 'build/testenv/lib/python3.6/site-packages/scipy/optimize/tests/test__differential_evolution.py::TestDifferentialEvolutionSolver::test_immediate_updating'

Thank you once again @rgommers for the review. I went through your comments, so modulo CI, it's back to you.

Merged! Thanks again @fuglede. Also for the excellent description and commit messages, very helpful for reviewing.


Convert component to React Native

I will work on this issue.

Hacktoberfest is over. Might reopen it next year.

On Sun, Nov 6, 2022 at 11:23 AM The Jared Wilcurt @.***>
wrote:

Hacktoberfest is over. Might reopen it next year.
—
Reply to this email directly, view it on GitHub
https://github.com/simple-donut/simple-donut-react-native/issues/1#issuecomment-1304837615,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIO35WSTQXATPNM4ZOIOGVTWG7ENLANCNFSM6AAAAAAQ6AQ2NM
.
You are receiving this because you were assigned.Message ID:
@.***>

Thanks for the opportunity. I’ll grab it next year if you reopen it.
-Bob


Phil/issue 91

@psaavedra CI failed with the meaningless errors:
ERROR: Job failed: Process exited with: 1. Reason was:  ()

The .gitlab-ci.yml is outdated respect changes done in the meta-perf-browser. MR #95  already fixed this and bumps up the wpewebkit 2.14.1


Add more layout object null checks

Followup to https://github.com/replayio/chromium/pull/253

Landing without review to fix crashes.


Decouple verifier from LLVM dependency by splitting //kythe/cxx/commo…

…n:lib some
This is the short-path to LLVM independence by re-implementing CleanPath inside kythe_uri.cc.  Ideally, we wouldn't depend on LLVM for path_utils and the header-search stuff would live elsewhere.
For now, this allows verifier to be built without LLVM.

I don't know what happened to those BUILD files, that was not what they looked like when I ran git commit

PTAL, seem to have resolved the mysterious BUILD reformatting (although there does seem to be a commit-hook-like behavior I'm not sure of the origin for), e.g.
$ git commit -m "Fix funky formatting on BUILD files"
[llvm-is-yuge 5577708a] Fix funky formatting on BUILD files
4 files changed, 740 insertions(+), 841 deletions(-)
rewrite kythe/cxx/common/BUILD (99%)
rewrite kythe/cxx/doc/BUILD (98%)
rewrite kythe/cxx/tools/fyi/BUILD (95%)
rewrite kythe/cxx/verifier/BUILD (98%)


Create a discussion listing business workflows to target

I'm submitting a ...
[ ] bug report
[X] feature request
[ ] question about the decisions made in the repository
[ ] question about how to use this project

Summary
Use Github discussions to start a discussion listing business workflow ideas we should target in this library. For example PII detection, Classification list for customer communications, Email communication rewriting, etc

I also have a question regarding the proposed workflows: would these workflows live in this repo, or are we considering creating a separate repository or module to handle them?

If its a quick example then we can add it to the examples folder for now. In the immediate future i'm working on a bit of an agents library where people can share agents for different tasks

I can tackle this. This is a pretty interesting use case.

Awesome reach out if you need anything. Also will be creating an org soon so larger agents etc can have their own repo


Cannot install v15 on Mac OS with M1 Chip

Operating system and version: macOS Big Sur 11.4
nvm debug output:

nvm --version: v0.38.0
$TERM_PROGRAM: iTerm.app
$SHELL: /bin/zsh
$SHLVL: 1
whoami: 'ppicom'
${HOME}: /Users/ppicom
${NVM_DIR}: '${HOME}/.nvm'
${PATH}: /opt/wildfly-16.0.0.Final/bin:JBOSS_HOME/bin:/opt/apache-ant-1.10.7/bin:/Library/Java/JavaVirtualMachines/jdk1.8.0_281.jdk/Contents/Home/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
$PREFIX: ''
${NPM_CONFIG_PREFIX}: ''
$NVM_NODEJS_ORG_MIRROR: ''
$NVM_IOJS_ORG_MIRROR: ''
shell version: 'zsh 5.8 (x86_64-apple-darwin20.0)'
uname -a: 'Darwin 20.5.0 Darwin Kernel Version 20.5.0: Sat May 8 05:10:31 PDT 2021; root:xnu-7195.121.3~9/RELEASE_ARM64_T8101 arm64'
checksum binary: 'shasum'
OS version: macOS 11.4 20F71
curl: /usr/bin/curl, curl 7.64.1 (x86_64-apple-darwin20.0) libcurl/7.64.1 (SecureTransport) LibreSSL/2.8.3 zlib/1.2.11 nghttp2/1.41.0
wget: /opt/homebrew/bin/wget, GNU Wget 1.21.1 built on darwin20.2.0.
sed: /usr/bin/sed
cut: /usr/bin/cut
basename: /usr/bin/basename
rm: /bin/rm
mkdir: /bin/mkdir
xargs: /usr/bin/xargs
git: /usr/bin/git, git version 2.30.1 (Apple Git-130)
ls: grep:: No such file or directory
grep: grep: aliased to grep --color=auto --exclude-dir={.bzr,CVS,.git,.hg,.svn,.idea,.tox} (grep --color=auto --exclude-dir={.bzr,CVS,.git,.hg,.svn,.idea,.tox}), grep (BSD grep) 2.5.1-FreeBSD
awk: /usr/bin/awk, awk version 20200816
nvm current: none
which node: node not found
which iojs: iojs not found
which npm: npm not found
npm config get prefix: nvm:282: command not found: npm
npm root -g: nvm:282: command not found: npm

nvm ls output:

            N/A
iojs -> N/A (default)
node -> stable (-> N/A) (default)
unstable -> N/A (default)
lts/* -> lts/fermium (-> N/A)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.17.1 (-> N/A)
lts/carbon -> v8.17.0 (-> N/A)
lts/dubnium -> v10.24.1 (-> N/A)
lts/erbium -> v12.22.1 (-> N/A)
lts/fermium -> v14.17.0 (-> N/A)

How did you install nvm?

Install script in readme
What steps did you perform?
First $ rm -rf "$NVM_DIR" to delete previous installation. Then run the script in the readme. After that, nvm install v15
What happened?
The tar.gz file for v15 downloads, then a little pause, then a stream of logs start appearing and it seems as if there is an error. The beggining of such logs:
Downloading and installing node v15.14.0...
Downloading https://nodejs.org/dist/v15.14.0/node-v15.14.0-darwin-arm64.tar.xz...

curl: (22) The requested URL returned error: 404
Binary download from https://nodejs.org/dist/v15.14.0/node-v15.14.0-darwin-arm64.tar.xz failed, trying source.
grep: /Users/ppicom/.nvm/.cache/bin/node-v15.14.0-darwin-arm64/node-v15.14.0-darwin-arm64.tar.xz: No such file or directory
Provided file to checksum does not exist.
Binary download failed, trying source.
Clang v3.5+ detected! CC or CXX not specified, will use Clang as C/C++ compiler!
Downloading https://nodejs.org/dist/v15.14.0/node-v15.14.0.tar.xz...
##################################################################################################################################################################################################### 100.0%
Computing checksum with shasum -a 256
Checksums matched!
©$>./configure --prefix=/Users/ppicom/.nvm/versions/node/v15.14.0 <
Node.js configure: Found Python 3.8.2...
No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.

No receipt for 'com.apple.pkg.DeveloperToolsCLILeo' found at '/'.

No receipt for 'com.apple.pkg.DeveloperToolsCLI' found at '/'.

Yes, I add things to the path but don't remove any.

After waiting for the process to complete I gathered all the logs. It seems that all this prompts were all warnings and that installation should work. I'd like to leave those logs here, if they can serve any purpose :)
nvm.log

It should not work; node only supports M1 on v16+.
Please see the relevant section in the readme.

node has experimental support for m1 on versions >=11 (see https://github.com/nodejs/node/blob/master/BUILDING.md#platform-list)

No receipt for 'com.apple.pkg.DeveloperToolsCLILeo' found at '/'.

maybe he did not install Xcode DeveloperTools,
I am installing with nvm install --lts (that's 14.17.1), now is building from source 😂
After a moment(15mins give or take) heavy-fan-working noises, build did complete.
❯ node
Welcome to Node.js v14.17.1.
Type ".help" for more information.
> os.arch();
'arm64'

Operating system and version: macOS Big Sur 11.4
nvm debug output:
nvm ls output:
How did you install nvm?
Install script in readme
What steps did you perform?
First $ rm -rf "$NVM_DIR" to delete previous installation. Then run the script in the readme. After that, nvm install v15
What happened?
The tar.gz file for v15 downloads, then a little pause, then a stream of logs start appearing and it seems as if there is an error. The beggining of such logs:
Downloading and installing node v15.14.0...
Downloading https://nodejs.org/dist/v15.14.0/node-v15.14.0-darwin-arm64.tar.xz...

curl: (22) The requested URL returned error: 404
Binary download from https://nodejs.org/dist/v15.14.0/node-v15.14.0-darwin-arm64.tar.xz failed, trying source.
grep: /Users/ppicom/.nvm/.cache/bin/node-v15.14.0-darwin-arm64/node-v15.14.0-darwin-arm64.tar.xz: No such file or directory
Provided file to checksum does not exist.
Binary download failed, trying source.
Clang v3.5+ detected! CC or CXX not specified, will use Clang as C/C++ compiler!
Downloading https://nodejs.org/dist/v15.14.0/node-v15.14.0.tar.xz...
##################################################################################################################################################################################################### 100.0%
Computing checksum with shasum -a 256
Checksums matched!
©$>./configure --prefix=/Users/ppicom/.nvm/versions/node/v15.14.0 <
Node.js configure: Found Python 3.8.2...
No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.

No receipt for 'com.apple.pkg.DeveloperToolsCLILeo' found at '/'.

No receipt for 'com.apple.pkg.DeveloperToolsCLI' found at '/'.

Yes, I add things to the path but don't remove any.

Is this problem solved, and how is it solved?

Is this problem solved, and how is it solved?

See the readme: https://github.com/nvm-sh/nvm#macos-troubleshooting under "Macs with M1 chip".
node doesn't officially support building on M1 prior to v15. You can build all node versions via Rosetta.
nvm doesn't really have anything to do with building node - it just invokes node's build commands. If there's something nvm can fix, I'll be happy to do it, but in this case there isn't - it's only something node can fix, or, you can open a rosetta terminal and install it there.

node doesn't officially support building on M1 prior to v15. You can build all node versions via Rosetta.

Did you ever read others' reply?  According to https://github.com/nodejs/node/blob/master/BUILDING.md#platform-list is Experimental support >= 11
And I did install (build) arm64 arch node v14.17.1 use nvm 0.38.0 (😄 Thank nvm a lot for it)

nvm doesn't really have anything to do with building node - it just invokes node's build commands. If there's something nvm can fix, I'll be happy to do it, but in this case there isn't - it's only something node can fix, or, you can open a rosetta terminal and install it there.

The issue author seems did not install DeveloperTools, and my  node install is arm64  indeed.
What he need to do, is just install xcode, and command line tools.

For the record,
my OS is macOS Big Sur 11.4  (on M1 SoC)
Xcode v12.5
* nvm -v
0.38.0
* node
Welcome to Node.js v14.17.1.
Type ".help" for more information.
> os.arch()
'arm64'

For the record,
my OS is macOS Big Sur 11.4 (on M1 SoC)
Xcode v12.5
* nvm -v
0.38.0
* node -v
v14.17.1
* node -p "process.arch"
arm64

compare to downloaded prebuilt bin for nodejs.org
* ~/Downloads/node-v14.17.3-darwin-x64/bin/node -p "process.arch"
x64

老哥，留个邮箱可否？

@hye i did, which is why i used the word “officially”. Experimental support doesn’t count.


wsclean - delete items before moving

In some circumstances the in memory temporary file system (the ramdisk) is used during wsclean in order to lighten the load on the larger filesystem. This is done through a context manager.
When the scope of the context manager is terminated, files in a watch directory are copied to a final location. It is only once the files have been copied are they examined while cleaning up. This cleaning up should be done while the data are still in memory.
Similarly, if fits cubes are being created from any subband images, these could be created and then moved.

This was done in #192


Improved FAQ readability with collapsible Q&A.

Changes

Changed Q&A from plain text to collapsible sections in README.md.
Fixed typo in FAQ answer.

For the lint Error, could you please fix it by following the instruction here?

It's passing locally, so I think it looks good if anyone can approve running the workflows.


Issue 309 - Adding transaction isolation and default to read committed

For issue #309. This adds an environment variable to the mariadb image that allows you to set the transaction isolation setting. It defaults to READ-COMMITTED now.
Related issues: https://github.com/Islandora/documentation/issues/1481 and https://github.com/Islandora-Devops/islandora-playbook/issues/250

Thank you @nigelgbanks for the feedback and for reviewing it. That makes sense to me and I made the changes that you recommended.


Post release followups

GitHub apparently decided i didn't need to know about you requesting I review this, so I only saw it today. :sweat:
It looks like this was completely replaced by #1540, so I'm going to close it. (This is trying to bump the version to 0.25.1, the other PR bumped the version to 0.25.2-prerelease.0 and was merged.)


Test-UI: Add stop discovery button when refreshing tests

Fixed via https://github.com/microsoft/vscode-python/pull/16892


Initially_open and initially_select

Hello. I'm currently using jstree v3.0.0 with ajax loading of the html data. It works perfectrly, but I need some nodes to be pre-opened and pre-selected. Is there any way to do this with ajax loading? adding initially_open:["id1","id2","id3"] didn't help at all. Nodes are not opened and not selected.
Thank you in advance

data.instance.set_state

What if I want to unselected note in this way, Can I do that?
e.g.
data.instance.set_state({ core : { opened : [full array of nodes here to open and load from the server], 'unselected' : [array of nodes to select] } })
Plz kindly advise


Missing documentation on Label position (Checkbox widget)

Dear doc team,
Checkbox has a special label position property Label position This feature is not documented, and is different from the form orientation.
This could be documented here; https://docs.mendix.com/refguide/common-widget-properties#label or https://docs.mendix.com/refguide/check-box#label

Why is there a Default (after) and an After control, are they the same? In tests I don't see a difference.
Or should this be equal to the Form orientation as set on the  Data view? In that case I expect an option Vertical to render the label above the checkbox.
Kind regards and cheers,
Andries

Just noticed, that the Default (after/before) change when the Read-only style change from Control to Text
Which makes some sense... as  :  in that case makes more sense that :

@Andries-Smit Thanks for the notes, I think @ConnorLand can take a look at this. In the future, an email or PR is preferred over a GitHub issue for such questions/updates. These issues are used for build/system questions.

@diego-antonelli can I look this over with you at your desk tomorrow?

Always my friendooo @ConnorLand


Add a Duplicate to the click-menu in the explorer pane

Feature request:
When right/ctrl-clicking on a file in the explorer, it would be helpful to have a Duplicate selection. This would copy and paste the selected file into another new file in the same directory.
My ideal would be to allow for a rename immediately after duplicate; alternatively it would just create the file with the filename-n name.
Currently this can be done with a ctrl-click copy and then a ctrl-click paste in the directory.

This would be a good candidate for an extension. @bpasero thoughts?

See this extension

Awesome. Exactly how I envisioned it. Thanks!

Thanks @hashhar


Using Semantic UI

How would one use Semantic UI with the starter kit?
This is what I tried:
npm install semantic-ui --save
cd semantic/
gulp build

I then try to reference the files in the src/index.html like this: <link rel="stylesheet" href="../semantic/dist/semantic.css" but that doesn't work
Any ideas on what I am doing wrong?

I successfully use semantic-ui in my project that was started from the starter kit. I admit, it took some trial and error to get it right. Your installation steps are good, and you built it -- good.  Since semantic ui is supposedly built with just the stuff you need (you can specify those in your semantic.json file), it shouldn't need any processing so it can be left out of webpack's business (mostly).
So, what you're probably missing...

Don't add anything to your index.html file
If you want semantic's javascript modules,

In src/main.js insert import 'semantic/dist/semantic' at the top. This dependency link will allow webpack to pull it in.

For the css styles, in src/styles/_base.scss, add @import url('/semantic/semantic.css');
In server/main.js, I have this configuration inside the development server if block:const compiler = webpack(webpackConfig)

// Enable webpack-dev and webpack-hot middleware
const { publicPath } = webpackConfig.output

app.use(webpackDevMiddleware(compiler, publicPath))
app.use(webpackHMRMiddleware(compiler))

// semantic files are in their own folder when running dev server.
// Use the production path in the html and for development this
// will rewrite the request.
app.use(convert(rewrite('/semantic/*', '/$1')))

// Serve semantic-ui assets for above reason
app.use(convert(serve(paths.client('semantic/dist'))))

// Serve static assets from ~/src/static since Webpack is unaware of
// these files. This middleware doesn't need to be enabled outside
// of development since this directory will be copied into ~/dist
// when the application is compiled.
app.use(convert(serve(paths.client('static'))))

You'll notice there's a url rewrite happening. Install koa-rewrite

Now, it should be working in development. There's a few more steps I highly recommend though:

When npm run deploy is executed, you will want semantic to be a part of it. In bin/compile.js, copy the semantic files to your dist folder.

line 18
debug('Copy static assets to dist folder.')
fs.copySync(paths.client('static'), paths.dist())

// Copy semantic-ui files to dist folder
// Should semantic-ui be rebuilt fresh on a deploy? (cd src/semantic && gulp build) I don't think so
debug('Copy semantic-ui to dist folder.')
fs.copySync(paths.client('semantic/dist'), paths.dist('semantic'))

- In `build/karma.conf.js`,
```javascript
# line 64
if (config.coverage_enabled) {
karmaConfig.reporters.push('coverage')
karmaConfig.webpack.module.preLoaders = [{
  test: /\.(js|jsx)$/,
  include: new RegExp(config.dir_client),
  loader: 'isparta',
  exclude: [/node_modules/, /semantic/]
}]
}

In build/webpack.config.js, you'll want the jquery variables added or semantic javascript functions won't be available to you:

line 44-ish
// ------------------------------------
// Plugins
// ------------------------------------
webpackConfig.plugins = [
new webpack.DefinePlugin(config.globals),
new HtmlWebpackPlugin({
template: paths.client('index.html'),
hash: false,
favicon: paths.client('static/favicon.ico'),
filename: 'index.html',
inject: 'body',
minify: {
collapseWhitespace: true
}
}),
new webpack.ProvidePlugin({
$: 'jquery',
jQuery: 'jquery',
'window.jQuery': 'jquery'
})
]
- In `/.eslintignore`, add `src/semantic`
- In `/.eslintrc`, add `$` to list of globals
- Line 34 of `tests/test-bundler.js` needs to be changed to `const componentsContext = require.context('../src/', true, /^((?!main)(?!semantic\/.*).)*\.js$/)` to not break your tests

Again, this is just how *I* got it working. It's by no means *the* solution since it is obviously very opinionated in what I did. I very much agree though that it was not a simple html include. I mean you could, but then the initial webpack build would take like 5 minutes.

One more unrelated, but helpful tip if you're using semantic. I would highly recommend using the `classnames

I successfully use semantic-ui in my project that was started from the starter kit. I admit, it took some trial and error to get it right. Your installation steps are good, and you built it -- good.  Since semantic ui is supposedly built with just the stuff you need (you can specify those in your semantic.json file), it shouldn't need any processing so it can be left out of webpack's business (mostly).
So, what you're probably missing...

Don't add anything to your index.html file
If you want semantic's javascript modules,

In src/main.js insert import 'semantic/dist/semantic' at the top. This dependency link will allow webpack to pull it in.

For the css styles, in src/styles/_base.scss, add @import url('/semantic/semantic.css');
In server/main.js, I have this configuration inside the development server if block:const compiler = webpack(webpackConfig)

// Enable webpack-dev and webpack-hot middleware
const { publicPath } = webpackConfig.output

app.use(webpackDevMiddleware(compiler, publicPath))
app.use(webpackHMRMiddleware(compiler))

// semantic files are in their own folder when running dev server.
// Use the production path in the html and for development this
// will rewrite the request.
app.use(convert(rewrite('/semantic/*', '/$1')))

// Serve semantic-ui assets for above reason
app.use(convert(serve(paths.client('semantic/dist'))))

// Serve static assets from ~/src/static since Webpack is unaware of
// these files. This middleware doesn't need to be enabled outside
// of development since this directory will be copied into ~/dist
// when the application is compiled.
app.use(convert(serve(paths.client('static'))))

You'll notice there's a url rewrite happening. Install koa-rewrite

Now, it should be working in development. There's a few more steps I highly recommend though:

When npm run deploy is executed, you will want semantic to be a part of it. In bin/compile.js, copy the semantic files to your dist folder.

line 18
debug('Copy static assets to dist folder.')
fs.copySync(paths.client('static'), paths.dist())

// Copy semantic-ui files to dist folder
// Should semantic-ui be rebuilt fresh on a deploy? (cd src/semantic && gulp build) I don't think so
debug('Copy semantic-ui to dist folder.')
fs.copySync(paths.client('semantic/dist'), paths.dist('semantic'))

- In `build/karma.conf.js`,
```javascript
# line 64
if (config.coverage_enabled) {
karmaConfig.reporters.push('coverage')
karmaConfig.webpack.module.preLoaders = [{
  test: /\.(js|jsx)$/,
  include: new RegExp(config.dir_client),
  loader: 'isparta',
  exclude: [/node_modules/, /semantic/]
}]
}

In build/webpack.config.js, you'll want the jquery variables added or semantic javascript functions won't be available to you:

line 44-ish
// ------------------------------------
// Plugins
// ------------------------------------
webpackConfig.plugins = [
new webpack.DefinePlugin(config.globals),
new HtmlWebpackPlugin({
template: paths.client('index.html'),
hash: false,
favicon: paths.client('static/favicon.ico'),
filename: 'index.html',
inject: 'body',
minify: {
collapseWhitespace: true
}
}),
new webpack.ProvidePlugin({
$: 'jquery',
jQuery: 'jquery',
'window.jQuery': 'jquery'
})
]
- In `/.eslintignore`, add `src/semantic`
- In `/.eslintrc`, add `$` to list of globals
- Line 34 of `tests/test-bundler.js` needs to be changed to `const componentsContext = require.context('../src/', true, /^((?!main)(?!semantic\/.*).)*\.js$/)` to not break your tests

Again, this is just how *I* got it working. It's by no means *the* solution since it is obviously very opinionated in what I did. I very much agree though that it was not a simple html include. I mean you could, but then the initial webpack build would take like 5 minutes.

One more unrelated, but helpful tip if you're using semantic. I would highly recommend using the `classnames` module for applying css styles. Importing individual class names like in the examples is tiresome with this library. And a lot of the dynamic stuff stops working.

Hi, i successfully integrate it too in the project : https://github.com/rsilvestre/react-redux-starter-kit/tree/semantic-ui
Thank you @beeftornado

Will add a recipe for this. Also see: https://github.com/TechnologyAdvice/stardust


Attribute Error: Can't pickle local object

Hi. Thank you for sharing!
I am trying to run with :
--ni --config celeba_hq.yml --doc celeba --timesteps 20 --eta 0.85 --etaB 1 --deg sr4 --sigma_0 0.05 -i celeba_hq_sr4_sigma_0.05
but I am getting:
Attribute Error: Can't pickle local object 'Diffusion.sample_sequence..seed_worker'
in the runners/diffusion.py?
is there any way around this?
thank you

Hi. Thank you for sharing! I am trying to run with : --ni --config celeba_hq.yml --doc celeba --timesteps 20 --eta 0.85 --etaB 1 --deg sr4 --sigma_0 0.05 -i celeba_hq_sr4_sigma_0.05 but I am getting: Attribute Error: Can't pickle local object 'Diffusion.sample_sequence..seed_worker' in the runners/diffusion.py? is there any way around this? thank you

@divastar Hello, I have the same problem as yours, did you solve the problem? If you have already solved this problem, could you please tell me how to solve it?
Thanks a lot!


PTFE-790 Ensure runner gets deleted from github

Codecov Report

Merging #408 (ce6daa8) into main (50f0c02) will decrease coverage by 19.15%.
Report is 9 commits behind head on main.
The diff coverage is 15.38%.

@@             Coverage Diff             @@
##             main     #408       +/-   ##
===========================================
- Coverage   83.18%   64.04%   -19.15%
===========================================
  Files          30       30
  Lines        1112     1118        +6
===========================================
- Hits          925      716      -209
- Misses        187      402      +215

Flag
Coverage Δ

api
64.04% <15.38%> (-0.35%)
:arrow_down:

unit
?

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

Files Changed
Coverage Δ

runner_manager/models/runner_group.py
58.37% <15.38%> (-30.63%)
:arrow_down:

... and 9 files with indirect coverage changes


CES-11261 Update Ironic undercloud patches

Raid.patch failing. Will send you the details @rpioso

Thank you, @gaelrehault. I uploaded a new commit to address the issue --  Fix raid.patch 3dd750c.

Looks good now


Feature: edit embed attribute command

The edit-embed-attribute command is now ready for use

The dev branch has been deleted, and the changes were pulled to main instead at https://github.com/SteeveMonkey/server-status-monitor_discord-bot/pull/2


__filename is not defined (ESM)

Package doesn't support ESM?
ReferenceError: __filename is not defined
node_modules/.pnpm/@contentful+node-apps-toolkit@2.8.2/node_modules/@contentful/node-apps-toolkit/lib/keys/get-management-token.js102:179
        defaultCache = new NodeCache();
    }
    const httpClientOpts = typeof opts.host !== 'undefined' ? { prefixUrl: opts.host } : {};
    return (0, exports.createGetManagementToken)((0, utils_1.createLogger)({ filename: __filename }), (0, utils_1.createHttpClient)(httpClientOpts), defaultCache)(privateKey, opts);
};
exports.getManagementToken = getManagementToken;

Should likely has an ESM supported build?
// Import the URL module to resolve file paths
import { fileURLToPath } from 'url'

// ESM replacement for __filename
const __filename = fileURLToPath(import.meta.url)

Hi @iDVB! Thanks for this feedback, I've created a ticket in our team's backlog and we will keep you updated on it's progress.


FPU more fflags issues and a few logic bugs

Describe the bug
This is continuation of the previous fflags issue. This is a mix of various float corner cases.
Each bug will have a detailed comment
Bug 1: fclass.s does not recognize subnormals correctly
Bug 2: feq, fle and flt do not treat subnormals as zero, do not correctly report NV for unordered numbers (q/sNAN), and fle had a logic bug of both numbers are negative and equal.
Bug 3: fmin/fmax do not treat subnormals as zero and do not report NV when a number is sNAN [still work in progress]
Bug 4: fsgnj, fsgnjn, fsgnjx uses the flushed subnormal number and not the real number.
Bug 5: multiplier with the fixed fclass the multiplier needs to self detect flushed subnormals. When OF/UF is detected NX isn't asserted. Post multiplication updated with subnormal as zero detection. [Still a work in progress]
Bug 6: Rounding modes does not round correctly, round to nearest towards +MAX added, bypasses added for rounds that cannot create infinity results.
Bug 7: Float to integer conversion has multiple issues with setting flags and handling corner cases.
I added the following to help with implementing subnormal support in a future FPU variant. Default is no sub-normal support in hardware.
  generic (
    -- FPU specific options
    FPU_SUBNORMAL_SUPPORT      : boolean := false -- Implemented sub-normal support, default false
  );

To Reproduce
See individual bug comments
Expected behavior
See individual bug comments
Screenshots
NA
Environment:

OS RHEL7
GCC Version 13.2
Libraries used newlib

Hardware:

Hardware version (<IP_ADDRESS>) patched with bug fixes

Additional context
See follow on comments for details

Bug #1: fclass does not support classifying subnormals
Prior to the classification the op signal has subnormals flushed, which it should as we are not supporting subnormals. But that means the actually classification is a tad tricky.
The following code snippet will correctly classify a subnormal number. The remaining classification code already supported subnormal usage.
      -- As we are flushing subnormals before classification they will show up as 0.0
      -- So we check calculate the denorm value is the non-flushed mantissa gated by the op_e_all_zero
      if (i = 0) then
        op_is_denorm_v := or_reduce_f(rs1_i(22 downto 0)) and op_e_all_zero_v; -- set the number to subnormal
      end if;
      if (i = 1) then
        op_is_denorm_v := or_reduce_f(rs2_i(22 downto 0)) and op_e_all_zero_v; -- set the number to subnormal
      end if;
      -- Placeholder for rs3_i support, as i cannot be 3.
      --if (i = 2) then
      --  op_is_denorm_v := or_reduce_f(rs3_i(22 downto 0)) and op_e_all_zero_v; -- set the number to subnormal
      --end if;

This had some follow on side effects all over the code base as we now signal a subnormal class we need to expand the conditions in quite a few places. E.g. zero detection in the addsub.
      -- shift right small mantissa to align radix point --
      if (addsub.latency(0) = '1') then
        -- check for denorm support
        if (FPU_SUBNORMAL_SUPPORT) then
          if ((fpu_operands.rs1_class(fp_class_pos_zero_c) or fpu_operands.rs2_class(fp_class_pos_zero_c) or
               fpu_operands.rs1_class(fp_class_neg_zero_c) or fpu_operands.rs2_class(fp_class_neg_zero_c)) = '0') then -- no input is zero
            addsub.man_sreg <= addsub.small_man;
          else
            addsub.man_sreg <= (others => '0');
          end if;
        else
          -- also use denorm for the check as we flush denorms.
          if ((fpu_operands.rs1_class(fp_class_pos_zero_c  ) or fpu_operands.rs2_class(fp_class_pos_zero_c)   or
               fpu_operands.rs1_class(fp_class_neg_zero_c  ) or fpu_operands.rs2_class(fp_class_neg_zero_c)   or
               fpu_operands.rs1_class(fp_class_pos_denorm_c) or fpu_operands.rs2_class(fp_class_pos_denorm_c) or
               fpu_operands.rs1_class(fp_class_neg_denorm_c) or fpu_operands.rs2_class(fp_class_neg_denorm_c)) = '0') then -- no input is zero
            addsub.man_sreg <= addsub.small_man;
          else
            addsub.man_sreg <= (others => '0');
          end if;
        end if;

Note the "FPU_SUBNORMAL_SUPPORT". This is used to select a path, as the existing zero detection code works correctly if we support subnormals. If we don't we need to add additional checks.

Bug #2: feq,flt, fle do not support subnormals and a logic bug.
As we are now reporting subnormals correctly there is additional conditions that have to be added to the compare section.
Basically comp_equal_ff and comp_less_ff have been extended with a subnormal path to treat subnormals as zero when FPU_SUBNORMAL_SUPPORT is false.
There was a logic bug in the FLT comparison where if rs1 and rs2 are both negative AND equal it will be FLT would return true. This as comp_less for negative numbers works as "<=" and not "<".
The fix is to gate cmp(cmp_less_c) with the zero indicator from the ALU, such that we get: "<=" and not "=".
          case cond_v is
            when "10"   => comp_less_ff <= '1'; -- rs1 negative, rs2 positive
            when "01"   => comp_less_ff <= '0'; -- rs1 positive, rs2 negative
            when "00"   => comp_less_ff <= cmp_ff(cmp_less_c); -- both positive (comparator result from main ALU)
            -- As we are just inverting cmp_less this statement would also flag true if the two numbers are equal
            -- Added a "and not equal" to prevent this corner case.
            when "11"   => comp_less_ff <= (not cmp_ff(cmp_less_c)) and (not cmp_ff(cmp_equal_c)); -- both negative (comparator result from main ALU)

The fle, flt and feq did not report NV when various unordered or sNAN values where used.
From the RISCV vol I specification:

The following code snippet fixes this issue:
    case ctrl_i.ir_funct3(1 downto 0) is
      when "00" => -- FLE: less than or equal
        fu_compare.result(0) <= (comp_less_ff or comp_equal_ff) and (not (snan_v or qnan_v)); -- result is zero if either input is NaN
        -- if one of the operands is unordered (q/sNAN) the compare operation must signal NV per 754.
        if ((snan_v or qnan_v) = '1') then
          fu_compare.flags(fp_exc_nv_c) <= '1';
        end if;
      when "01" => -- FLT: less than
        fu_compare.result(0) <= comp_less_ff and (not (snan_v or qnan_v)); -- result is zero if either input is NaN
        -- if one of the operands is unordered (q/sNAN) the compare operation must signal NV per 754.
        if ((snan_v or qnan_v) = '1') then
          fu_compare.flags(fp_exc_nv_c) <= '1';
        end if;
      when "10" => -- FEQ: equal
        fu_compare.result(0) <= comp_equal_ff and (not (snan_v or qnan_v)); -- result is zero if either input is NaN
        -- if one of the operands in the compare operation is a sNAN we must signal NV per 754.
        -- for equal compares we do not need to consider unordred NAN
        if ((snan_v) = '1') then
          fu_compare.flags(fp_exc_nv_c) <= '1';
        end if;
      when others => -- undefined
        fu_compare.result(0) <= '0';

Bug #3: adding support for subnormals as zero. Do not flag sNAN as NV.
Added additional conditions to the cond_v generation that treats subnormals as zero if FPU_SUPPORT_SUBNORMAL is false.
fmin and fmax where not reporting NV when one input is sNAN. From the RISCV Vol I specification:

The fix is to detect sNAN and assert the NV flag.
    -- exceptions --
    -- Assume no exceptions
    fu_min_max.flags <= (others => '0');
    -- if one of the operands is sNAN) the compare operation must signal NV per 754 2019 chapter 9.6
    if ((fpu_operands.rs1_class(fp_class_snan_c) or fpu_operands.rs2_class(fp_class_snan_c)) = '1') then
      fu_min_max.flags(fp_exc_nv_c) <= '1';
    end if;

This bug is not 100% closed as there are some challenges with e.g max(0.0, -0.0) in the reference model.

Bug #4: fsgnj, fsgnjn, and fsgnjx are using the flushed subnormal and not the subnormal itself.
Added a FPU_SUBNORMAL_SUPPORT gate, granted might not be needed as it will always work. Prefered to be consistent :)
    -- if we do not have subnormal support we need to use the input operand and not the
    -- converted operand
    if (not FPU_SUBNORMAL_SUPPORT) then
      fu_sign_inject.result(30 downto 0) <= rs1_i(30 downto 0);
    else
      fu_sign_inject.result(30 downto 0) <= fpu_operands.rs1(30 downto 0);
    end if;

bug 6: Rounding modes:
Added two new floating point constants to the package file to assist with rounding functions:
  constant fp_single_pos_max_c  : std_ulogic_vector(31 downto 0) := x"7f7FFFFF"; -- positive max
  constant fp_single_neg_max_c  : std_ulogic_vector(31 downto 0) := x"Ff7FFFFF"; -- negative max

Added support for round to nearest, ties to max magnitude.
      when "100" => -- round to nearest, ties to max magnitude
        -- similar to rount to nearest, ties to even. This is basically "classic" round
        -- if the remainder is <0.5 (g = 0) we truncate
        if (sreg.ext_g = '0') then
          round.en <= '0'; -- round down (do nothing)
        else -- the remaind is >= 0.5 (g = 1) we round up
          round.en <= '1'; -- round up
        end if;
        round.sub <= '0'; -- increment

Removed the '0' mask bit in the FRM CSR transfer.
          -- rounding mode --
          -- TODO / FIXME "round to nearest, ties to max magnitude" (0b100) is not supported yet
          if (ctrl_i.ir_funct3 = "111") then
            fpu_operands.frm <= csr_frm(2 downto 0);--'0' & csr_frm(1 downto 0);
          else
            fpu_operands.frm <= ctrl_i.ir_funct3(2 downto 0); --'0' & ctrl_i.ir_funct3(1 downto 0);
          end if;

Round towards +/- infinity did not take sign into account.
      when "010" => -- round down (towards -infinity)
        -- If the number is positive truncate to round down towards -inf
        if (sign_i = '0') then
          round.en <= '0'; -- truncate
        else -- if the number is negative and we have a remainder increment to round up towards -inf
          round.en  <= sreg.ext_g or sreg.ext_r or sreg.ext_s;
          round.sub <= '0'; -- decrement
        end if;
      when "011" => -- round up (towards +infinity)
        -- if the number is negative truncate to round down towards +inf
        if (sign_i = '1') then
          round.en <= '0'; -- truncate
        else -- if the number is positive and we have a remainder increment to round up towards +inf
          round.en  <= sreg.ext_g or sreg.ext_r or sreg.ext_s;
          round.sub <= '0'; -- increment
        end if;

In case of overflow the normalizer would inject +/- infinity. This is incorrect behavior per IEEE754. Per chapter 4.3.2 Directed Rounding Attributes roundTowardZero can never produce and infinite result. For roundTowardPositiveInfinity can never product a negative infinity and the reverse for roundTowardNegativeInfinity.
This has now been fixed.
          elsif (ctrl.class(fp_class_neg_inf_c) = '1') or (ctrl.class(fp_class_pos_inf_c) = '1') or -- infinity
                (ctrl.flags(fp_exc_of_c) = '1') then -- overflow
            -- if rounding mode is towards 0 we cannot generate an infinity instead we need to generate +MAX
            if ((rmode_i = "001") and (ctrl.flags(fp_exc_of_c) = '1')) then
              ctrl.res_exp <= fp_single_pos_max_c(30 downto 23); -- keep original sign
              ctrl.res_man <= fp_single_pos_max_c(22 downto 00);
            -- if rounding mode is towards -inf we cannot generate a positive infinity instead we need to generate +MAX
            elsif ((rmode_i = "010") and (ctrl.flags(fp_exc_of_c) = '1') and (sign_i = '0')) then
              ctrl.res_exp <= fp_single_pos_max_c(30 downto 23); -- keep original sign
              ctrl.res_man <= fp_single_pos_max_c(22 downto 00);
            -- if rounding mode is towards +inf we cannot generate a negative infinity instead we need to generate -MAX
            elsif ((rmode_i = "011") and (ctrl.flags(fp_exc_of_c) = '1') and (sign_i = '1')) then
              ctrl.res_exp <= fp_single_neg_max_c(30 downto 23); -- keep original sign
              ctrl.res_man <= fp_single_neg_max_c(22 downto 00);
            else
              ctrl.res_exp <= fp_single_pos_inf_c(30 downto 23); -- keep original sign
              ctrl.res_man <= fp_single_pos_inf_c(22 downto 00);
            end if;

With these changes all riscvof-arch fadd/fsub tests pass.

Bug 5: Multiplier exception handling.
The multiplier didn't correctly identify zero operands which causes some errornous results from multiplications of zero * zero.
When inputs to the multiplier was +/-INF, sNAN or qNAN the wrong exception flags where generated.
Invalid flags were not set correctly.

Bug 7: Float to integer conversion has missing flag settings, some incorrect rounding and missing exception handling.
This is probably the highest touch area for the FPU. Of note are:
Float to int conversion can only generate NV and NX flags. Per IEEE and RISCV spec DZ, OF and UF cannot be generated. This has been fixed.
The flag_o port was only held correct while done was  but the CSRs captured it the cycle later, so needed to add flags to the ctrl_t and remember the flag settings.
G and R guard bits where not set correctly. They basically where always set to the top 2 bits, which works sorta unless we are <0.5 or overflows. This has been changed to ensure that G, R and S are all set correctly for rounding to work appropriately. This change is in the F2I state.
Underflow was not signaled correctly for very small numbers.
For left shits G, R and S are held at 0 as they will never be set.
NX flag set in S_ROUND state to correctly indicate inexact.
S_FINALIZE has been majorly expanded to handle all sorts of "fun" corner cases for float to integer. Quite a few of the larger if statements have been broken out to better manager the exception flag setting.
As we don't have an overflow (shift left) S (sticky) bit, which would be set when a "1" is shifted out to the left there is a notorious worst case for signed conversion where the floating point number is exactly -2^32 that got flagged as overflow.

Currently running a regression run to ensure all the bug fixes are working correctly. Will push a PR afterwards.
There are some caveats to the passing test, which is the reference testing. As the Sail simulator used for the reference test runs the code with subnormal support, there are some compares that will fail because of this. Working on a fix to the reference code generation to prevent this.
We have one test case: block_sim/rv32i_m_Zfinx_fcvt.wu.s_b24 which fails vs the Sail reference bit passes our Imperas reference model. The error here is a disagreement on the NX flag. Sail says NX we say no-NX. Its about 6 cases but need to review them to be able to waive them.

PR #794 created.

Another great input! Thank you very much, @mikaelsky!
Give me some time to look through this... 😅

I know, its a lot :)


Test Checkout Flow With Tabbing

For accessibility, you should be able to get through the site without a mouse or finger...actually, I don't know how that would work with a touch screen.
I tried tabbing through things briefly and it did not go well.

added to cu-giving tests.


FEATURE(aamwriter): implemented aamwriter.

Generator of AAM from json topology) and REST endpoint.
This PR adds:

a module to planner (planner/aamwriter), where resides the functionality of the aamwriter;
a REST endpoint to the dashboard (POST /api/aamwriter/translate)

Usage:
cd planner/aamwriter
java -jar target/aamwriter-jar-with-dependencies.jar <topology.json>

curl -v -H"Content-type: application/json" -X POST<EMAIL_ADDRESS>http://localhost:8000/api/aamwriter/translate

There are examples in src/main/resources/examples/.

@rosogon I've a general comment: is it possible to generate a YAML representation from the GUI, without generating json first that need to be translated then?

The json file is actually the tree of objects that represent the topology in memory, and is used by the d3 and the code that handles the forms. So, in any case, a translation to TOSCA must be implemented, either in javascript in the client or in the server.

One last comment is about squashing the two commits into a single one.
After that I think we can merge

@rosogon I was wondering why haven't you used the a4c classes like NodeType or ArchiveRoot instead of implementing your own?
I think we spent a lot of effort for the ToscaParser and we should use it as much as possible: that's why it is in common module, after all.
Thoughts?
Thanks

Simone suggested me to build a snake yaml object and serialise that ("Unfortunately with a4c only the topology is serializable unless you want to extend their serializer"). And we are using in the AAM node_types and groups.

@rosogon do you think we could use this library http://jsontoyaml.com/#javascript instead?
Looks like it is able to transform json-formatted objects into yaml-formatted objects quite easily, so that we can avoid the java rest endpoint ?


Enhancement — Check for DIDs the alternative way

i.e. GET /xrpc/com.atproto.identify.resolveHandle can return a JSON {'did': '<did>'} and that's also valid (that's how alice.bsky.sh is set up because wildcard domains)

Closed by #18


IgnoreNonReplicatedObjects filter may filter out the wrong array indices.

https://github.com/xyahh/UE4RuntimeTransformer/blob/462df38f56ae7f7c004072dbbabd9e68312e2d64/RuntimeTransformer/Source/RuntimeTransformer/Private/TransformerPawn.cpp#L130
Using the above code as context, the moment outHits.RemoveAt(i) is triggered, the array will shrink and thus will not be the same length as checkHits. Meaning that the next time this line of code is called, it will remove the wrong index because the indices shifted.

You are completely right! I should be using the Iterators for that!
On Tue, Jan 19, 2021 at 6:36 AM HiIAmMoot<EMAIL_ADDRESS>wrote:

https://github.com/xyahh/UE4RuntimeTransformer/blob/462df38f56ae7f7c004072dbbabd9e68312e2d64/RuntimeTransformer/Source/RuntimeTransformer/Private/TransformerPawn.cpp#L130
Using the above code as context, the moment outHits.RemoveAt(i) is
triggered, the array will shrink and thus will not be the same length as
checkHits. Meaning that the next time this line of code is called, it will
remove the wrong index because the indices shifted.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/xyahh/UE4RuntimeTransformer/issues/5, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHTOOC2I7V4GHQ6EUNXHO63S2SSVFANCNFSM4WH3QHPQ
.

You are completely right! I should be using the Iterators for that!
On Tue, Jan 19, 2021 at 6:36 AM HiIAmMoot<EMAIL_ADDRESS>wrote:

https://github.com/xyahh/UE4RuntimeTransformer/blob/462df38f56ae7f7c004072dbbabd9e68312e2d64/RuntimeTransformer/Source/RuntimeTransformer/Private/TransformerPawn.cpp#L130
Using the above code as context, the moment outHits.RemoveAt(i) is
triggered, the array will shrink and thus will not be the same length as
checkHits. Meaning that the next time this line of code is called, it will
remove the wrong index because the indices shifted.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/xyahh/UE4RuntimeTransformer/issues/5, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHTOOC2I7V4GHQ6EUNXHO63S2SSVFANCNFSM4WH3QHPQ
.

Thanks for the heads up ;)
On Tue, Jan 19, 2021 at 9:27 AM Juan Marcelo Portillo <
<EMAIL_ADDRESS>wrote:

You are completely right! I should be using the Iterators for that!
On Tue, Jan 19, 2021 at 6:36 AM HiIAmMoot<EMAIL_ADDRESS>wrote:

https://github.com/xyahh/UE4RuntimeTransformer/blob/462df38f56ae7f7c004072dbbabd9e68312e2d64/RuntimeTransformer/Source/RuntimeTransformer/Private/TransformerPawn.cpp#L130
Using the above code as context, the moment outHits.RemoveAt(i) is
triggered, the array will shrink and thus will not be the same length as
checkHits. Meaning that the next time this line of code is called, it will
remove the wrong index because the indices shifted.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/xyahh/UE4RuntimeTransformer/issues/5, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHTOOC2I7V4GHQ6EUNXHO63S2SSVFANCNFSM4WH3QHPQ
.

Thanks for the heads up ;)
On Tue, Jan 19, 2021 at 9:27 AM Juan Marcelo Portillo <
<EMAIL_ADDRESS>wrote:

You are completely right! I should be using the Iterators for that!
On Tue, Jan 19, 2021 at 6:36 AM HiIAmMoot<EMAIL_ADDRESS>wrote:

https://github.com/xyahh/UE4RuntimeTransformer/blob/462df38f56ae7f7c004072dbbabd9e68312e2d64/RuntimeTransformer/Source/RuntimeTransformer/Private/TransformerPawn.cpp#L130
Using the above code as context, the moment outHits.RemoveAt(i) is
triggered, the array will shrink and thus will not be the same length as
checkHits. Meaning that the next time this line of code is called, it will
remove the wrong index because the indices shifted.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/xyahh/UE4RuntimeTransformer/issues/5, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHTOOC2I7V4GHQ6EUNXHO63S2SSVFANCNFSM4WH3QHPQ
.


Auto close with white screen on android

Version
0.1.3
Problem Area
react-native-pytorch-core (core package)
Steps to Reproduce
No bugs show up by following manual set up tutorial. But when I open the app, the app close itself with an instant white screen.
Two tutorial get the same result.
https://pytorch.org/live/docs/tutorials/get-started-manually/
https://pytorch.org/live/docs/tutorials/image-classification/
I think my connection is OK, beacuse react native tutorial works fine.
Systems: Ubuntu 20 + python 3.9.7
Expected Results
Get a functional application, not just an app icon.
Code example, screenshot, or link to repository

npx react-native start show something weired once I try to open app on my android device:

Hi @anthonyweidai thanks for reporting and sorry about the issue!
For now the react-native-pytorch-core package is only fully tested/supported on Mac OS. We would like to support Ubuntu in the future once we have more bandwidth, but for now we may have to rely on the community for this support.
With that said, running the app with Android Studio may log more useful debug info if you have one installed. Please let us know if that helps?

Hi @anthonyweidai, thanks for your report!
If the React Native tutorial works with your devices, then the PyTorch Live tutorials should work as well.

Can you provide more information on the physical device (i.e., model, OS, OS version)?
Does the app build and install correctly on the physical device, but crash when the app is opened?
Can you install and open Flipper, which will receive a crash report. This crash report would be super useful for us to debug the issue.

Info about Flipper in React Native documentation

Thank you!


Add ability to delete users (rebase of #2523)

#2523 rebased with some cleanup and extra tests - opening a new PR to run through CI

Merged in 14919f3b41da8d089c870975bcd0364af6176d59


Icons vanishing

Having weird issue where during deployment or if we update a local/staging instance of site with the production one then we have to redeclare the folders used/available for specific fields. If we don't then it loses all the SVG references for specific entries. Bit of a ball ache for an otherwise great plugin.
Any thoughts on resolving or can anyone confirm similar?

ah, can see in field settings that absolute paths are being saved. any way to make this relative or easier to migrate between contexts?

Have sent a pull request to offer use of a dynamic variable {document_root} when specifying the iconSetsPath within a svgicons.php config file.


Error when issuing a wildcard certificate on Windows

From the error logs seems wildcard certificate related data is placed in a folder with a invalid name:
[Fri Apr 10 17:14:14.598191 2020] [md:error] [pid 19856:tid 644] (OS 123)The filename, directory name, or volume label syntax is incorrect.  : rename from C:/path/to/apache/md/staging/redacted.example.com to C:/path/to/apache/md/staging/*.redacted.example.com
[Fri Apr 10 17:14:14.598191 2020] [md:error] [pid 19856:tid 644] (OS 123)The filename, directory name, or volume label syntax is incorrect.  : AH10073: syncing 1 mds to registry

Checking this StackOverflow answer * can be used in filenames in Linux/Unix but not Windows.

While it is legal to use '*' in filenames on Unix (and VMS many others), it's never a good idea.  Someone always goes to delete the file without the proper quoting.  As far back as the 1960s, I remember "pranksters" creating such files in someone else's directory, and watching as their target deleted their work...  Back then, the prankster usually was nice enough to have saved a backup copy for the target.  But those were gentler times.  You also wouldn't want a filename of example.txt>/etcpasswd...legal, but unwise.
mod_md needs to replace the '*' with some other token.  Unfortunately, there aren't good choices.
_wild would seem like a good choice - '_' isn't valid in a DNS hostname.  But it is valid in a DNS label (e.g. see RFC 2782, which uses _service.__proto - e.g. _ldap._tcp.example.com).  ACME supports certificate subjects other than hostnames, so we need to be careful not to run into this in a future case.  (e.g. a certificate issued for an e-mail address, or a person's name.)
Probably the safest thing to do is to create the filename by hashing the subject - which means either an index or reading each file to look for an unknown subject name.  The hash cand be constrained to e.g. [A-Z0-9-] (some filesystems are case insensitive).
Alternatively, an escaping scheme could be used, e.g. _hexcode_ for any characer not in a safe list.  (With _ being _3f_. Bracketing the code allows for wide characters.)   That's easier for humans to read and doesn't require opening the file to learn the domain name, though it might take a couple of iterations to establish a "safe" list that works for all OSs on which httpd runs.  And because it expands the name it can run into length limits on filenames.
Unfortuately, either choice also means a database conversion when that version of mod_md is released.   It's very doable, but does require more code.  Sigh.
@icing should probably handle this one.
Meantime, you might try using one of the covered names as the domain name, and make the wildcard an MDMember.  It's harmless to include a hostname that's also covered by the wildcard.  (E.g.  <MDDomain www.example.net><MDMember *.example.net></MDDomain>  or <MDDomain www.example.net *.example.net>)  The files store entire domains - I don't think there's a case where a domain member is used as a filename.
That should work for any client that checks the SANs for a wildcard, but if the CN must be a wildcard, you'll have to wait for a complete fix.

I prefer the wildcard being a SAN, but if I configure like that DNS verification fails. Seems that it sets the TXT for both hostnames first then tries to verify instead of setting the TXT then verify for each hostname in other. The DNS service I'm using allows changing TXT records, but only globally, in other words, if you set TXT records for both hostnames first then just the last record will be saved as it will overwrite the first.

The validator is doing the right thing.  Otherwise you'd run into a number of timing issues with caches...
That sounds like a bug with either the DNS service or the client.  You can have any number of TXT records in a domain.  But DNS operators are notorious for unique (and broken) update mechanisms.  RFC 2136 is largely ignored...
I ran into something like this when updating GoDaddy DNS - they don't have an API for adding to a RRSET; you have to replace the whole set.  That means update requires reading all the existing TXT records, removing only those that you don't need any more, adding any new ones, then replacing the whole RRSET.  (Obviously, there are race conditions with multiplel updaters...)  It's possible to make it work for this use case.
I don't see how what you described can work in practice, though.  Are you sure that a given domain can have only one TXT record?  Most have many - a TXT record for SPF, one for Google statistics, and various others.  So it seems most likely that the issue is in whatever tool you're using to make the updates.  For example:
isc.org.                7156    IN      TXT     "MS=2583E0E0DCCBF33EC6DAFF0B4BFBAF78FFCF7AD0"
isc.org.                7156    IN      TXT     "google-site-verification=wg4m8dWi3XVPRYmtBoy6xSKp3juhxIWa6UdxjZkNQCg"
isc.org.                7156    IN      TXT     "v=spf1 a mx ip4:<IP_ADDRESS>/21 ip4:<IP_ADDRESS>/16 ip6:2001:04F8::0/32 include:servers.mcsv.net ip6:2001:500:60::65/128 ~all"
isc.org.                7156    IN      TXT     "google-site-verification=6v652rgkk_kI6Ky32iGdxqXjQ4_BAd5DYKsrnRXKUiE"
isc.org.                7156    IN      TXT     "_globalsign-domain-verification=ckxXdoIq27XGYE4ATbBYQOBeV7PTJWRxYe-PXDyzMX"

Or, two hosts in one domain:
hagrid.sb.litts.net.    86400   IN      TXT     "v=spf1" " ip4:<IP_ADDRESS>" " ip4:<IP_ADDRESS>" " ip4:<IP_ADDRESS>" " ip4:<IP_ADDRESS>" " ip4:<IP_ADDRESS>" " ip6:2001:470:8f95:940::/60" " a:micro.litts.net" " a:nano.litts.net" " a:pico.sb.litts.net" " a:overkill.sb.litts.net" " a:hagrid.sb.litts.net" " a:smtp.litts.net" " -all"
overkill.sb.litts.net.  86400   IN      TXT     "v=spf1" " ip4:<IP_ADDRESS>" " ip4:<IP_ADDRESS>" " ip4:<IP_ADDRESS>" " ip4:<IP_ADDRESS>" " ip4:<IP_ADDRESS>" " ip6:2001:470:8f95:940::/60" " a:micro.litts.net" " a:nano.litts.net" " a:pico.sb.litts.net" " a:overkill.sb.litts.net" " a:hagrid.sb.litts.net" " a:smtp.litts.net" " -all"

I added DNS update scripts for various providers (from another project) to the mod_md repo recently as part of some work-in-progress.   You might find some answers there.
I haven't needed LE wildcards though - so no promises that those scripts will work as-is for you.

I know that's possible because I also work with other services, but it's a limitation of this service: as their documentation says "your TXT record will apply to all sub-subdomains under your domain". I can use other service of course which don't have this limitation, but that's not in my plans at the moment.
I used other LE clients before and some had this issue, others don't. If you say the implementation is correct, well, I'm fine with that, I had other issues with other clients anyway.

I'm saying that LE's validator is doing the right thing.
I agree with you that mod_md should not be trying to create (or read) a file name containing `*``.
Who is the DNS service that you use?
I could read the sentence that you quote as "software that reads the TXT record will (may) apply it to subdomains" - which is reasonable, if technically incorrrect.  Some software will, some won't.  They may be describing a particular use case.  That shouldn't preclude others.
Or as you have, that "you can't create TXT records for more than one subdomain/host in a domain".  That may be true - but if so, it's clearly wrong.
It's very reasonable to want several TXT records for several hosts for other use cases.  For example,
you have two hosts, and the TXT records are SPF policies, which are different.  Or they're the contact information for security events - and you have two different IT groups. Or...
In any case, you have a valid use case (LE wildcard validation), and your provider needs to support it.
Your service provider deserves a bug report from you.  Either their documentation is confusing, or their API needs work.  Or maybe both!
As for mod_md, I'm sure @icing will put this issue on his TODO list.

Also - whether the wildcard is primary or only in the SAN list, LE will still need to validate two TXT records for it.
So I suspect that while you're encountering the filename issue in mod_md when the request is recorded,  your DNS provider issue will be encountered at the next step even when it is fixed.  Why do you think that the validation sequence will be different if the wildcard is primary?
I'm confused.  You indicate that validation succeeds in that case.  For that to be true, I think you must be encountering a timing/caching issue.  Something like because of propagation time, the validator sees one TXT record after you've deleted/replaced it with the second.  If this is true, it wouldn't be reliable.  Relying on timing would be a bad idea - in addition to the validator's workload being unpredictable, note that LE is starting to validate each record from multiple servers, which are in different places on the network. I must be missing something.
I also noticed a LE post on wildcards that says they will reject redundant requests such as *.example.net, www.example.net.  So a SAN work-around for this issue might have to be a bit more creatitve, e.g. dummy-host.x.example.net, *.example.net.  (Wildcards in DNS only apply to a single, terminal level.)  dummy-host.x.example.net would not exist, but LE would validate it as ususal.
I agree that mod_md has a bug that should be fixed.  But I don't see how LE wildcards can work with a DNS service that won't provision 2 TXT records in a domain.

Check documentation, it's just how it works. I thought it was possible to verify one hostname, store the verification, verify the other and then use both verifications to get the certificate. If that's not possible then I can use two certificates, one just for the wildcard. It's just for a development server: I plan in future to use wildcards to I can test multiple projects more easily. I will wait for the filename issue to be fixed.

That's a very strange service - it doesn't conform to the DNS RFCs.  Note that they do say

This can be used for example to prove your ownership with letsencrypt.org

So why not send DuckDNS a bug report and point out that they don't support wildcard DNS from LE?  Seems like something that they can fix.  They have a forum at https://groups.google.com/forum/#!forum/duckdns
Again, even when the filename issue is fixed, I don't think this service will work until they meet LE's requirement to provision two distinct TXT records.
Verification is not driven by mod_md.  LE tells mod_md (or any client) what it wants, and mod_md responds.  It's LE that requests/tracks verifications.  mod_md is passive in that process.
The sequence is roughly:

C: Please issue a certificate (mod_md writes a file to track the progress) - this is where we stop now
S: To prove you own the domain, install these records
C: (installs records)
C: Ready for you to check my work
C: Are you done yet (repeats)
S: Checks DNS for both records - this is where I think you'll fail once the filename is fixed
S: Yes, you can delete the records.  Here's where to get your certificate.

I believe that LE does cache verification results - but for wildcards, the verification doesn't have a result until both records are successfully seen.
In any case, for webserver projects, a wildcard doesn't save much work.  mod_md will detect that you've added a new VHOST and request a new certificate automatically.  Since there is no charge, there's really no reason to use a wildcard certificate for that.  If you are using the certificate for a lot of other applications, (mail, new, notes,...) it may be easier to have a wildcard than to update all of them.  Or if you have a LOT of vhosts (LE supports ~100/per certificate), a wildcard certificate is smaller, which conserves network bandwidth.

I prefer wildcards over automatic certificate creation because in this way subdomains don't show up in certificate transparency logs, but I will consider that for future projects. I also could run my own CA, as that's just for local development, but from what I read I find it harder to set up than using LE.

@tlhackque About the DuckDNS issue I've said "I used other LE clients before and some had this issue, others don't.". After searching a bit seems there is a small issue with your explanation: as shown here it will work if the client don't all challenges in a batch, I just got it working now.
Probably it's hard to implement it here and, of course, it's slower, so I don't expect it being fixed here, I just wanted to share this info.

Closed as being stale.


[RFE] Find a way to provide bpftrace for arm64

Current situation
[ Please describe the current situation you would like to have improved ]
Impact
[ Please describe the impact the lack of the feature requested is creating ]
Ideal future situation
[ Please describe the future situation after the improvement was implemented ]
Implementation options
[ Optional: please provide one or more options for implementing the feature requested ]
Additional information
[ Please Add any information that does not fit into any of the above sections here ]

I made some progress in https://github.com/inspektor-gadget/bpftrace/commit/655f19550458c1f16e1acfd8ba2b891df6794779, feel free to take it if you think it's useful.

After 4 hours of cross compilation on my machine, I was able to push the image to https://hub.docker.com/repository/docker/mauriciovasquezbernal/bpftrace/general. I haven't try it out with Inspektor Gadget yet.

I tested it and works fine on arm64, the image I used is in https://hub.docker.com/repository/docker/mauriciovasquezbernal/gadget/.
We need to think about the compilation time, specially for the llvm image since it takes  time is 4hours in my machine. I don't think it's suitable for github actions.

I need to be more clear about my terminology. I used docker buildx with qemu to emulate the whole compilation on arm64.


Document the various Method and BasicMessage channels

We have a number of communication channels that are used for different purposes, and their expected usage is not documented.  Also, for creating new channels, the expected scope and naming conventions of channels are also not defined.
Some examples of existing channels:
flutter/accessibility
flutter/assets
flutter/keyevent
flutter/lifecycle
flutter/localization
flutter/navigation
flutter/platform
flutter/settings
flutter/system
flutter/textinput

Each one should be documented.
Some examples of files where they are used:
shell/common/engine.cc
shell/platform/android/io/flutter/view/FlutterView.java
shell/platform/darwin/ios/framework/Source/FlutterViewController.mm

Ideally this documentation would end up in the API docs somehow.

One place to define them would be on the Dart classes, e.g. https://master-docs-flutter-io.firebaseapp.com/flutter/services/SystemChannels-class.html

I tried to add some docs a while back but we should add more.


Initial sprint: Servant + Persistent

Already implemented:

Authentication
Basic app architecture
Persistent models for Tenant and User

Goals for Fri 21/10/16:

Typesafe way to handle updates/edits to entities(Tenant/Users/Products etc.)
Domain API for Tenant:

createTenant
activateTenant
updateTenant
getTenant

Domain API for User:

createUser
editUser
getUser
activateUser
deactivateUser

Experiment with type safe ways of handling roles and permissions.

Related PR: https://github.com/vacationlabs/haskell-webapps/pull/30


Fix duplicate requirements specification

What is the goal of this PR?
This PR solves issue #219 by including requirements.txt inside of requirements_dev.txt, so that the requirements are no longer duplicated. Going forward, developers will no longer need to remember to copy changes from requirements.txt to requirements_dev.txt.
What are the changes implemented in this PR?
This PR adds a reference (-r requirements.txt) to requirements_dev.txt, and cleans up the instructions around it. See the pip install Requirements File Format for details on this feature.
closes #219

Thank you for the contribution!


[TASK] ARMA Fourier splitting in ROMCollection

Issue Description
User control over how the Fourier bases are split between Global and Local analysis in the ARMA when used in the ROMCollection would be useful for flexibility and accuracy of generated synthetic signals.

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[x] 1. Is it tagged with a type: defect or task?
[x] 2. Is it tagged with a priority: critical, normal or minor?
[x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[x] 1. If the issue is a defect, is the defect fixed?
[x] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[x] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[x] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
[x] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?

Checklist passed.
Closure approved via #1409

Checklist passed.
Closure approved via #1409


Enable coveralls

Changes Unknown when pulling b9194ace738126897bd20549d16188b8924d9e6e on coveralls into ** on master**.

Changes Unknown when pulling 53c043513f39f9264de2dd5501db3800c5d597f2 on coveralls into ** on master**.


fix: do not hardcode page sizes

Hello,
I had a use-case for a different page size (i.e. higher dpi). However, manually providing width and height to the page broke the speaker notes feature. Just replacing the hard-coded values with the actual page size seems to just work fine.

Thanks.


Add wstaeblein repos

Your PR have formatting issue.
Can you run pnpm run format to solve them?

Your PR is also in conflict as another PR was merged before yours, so if you can rebase it, it would be great.

Hi @wstaeblein , thanks for your submissions! Unfortunately, the components.json file requires packages to be published on NPM, since we obtain metadata about the package from here. I understand these are simple components, however it also isn't straight-forward for a user to find the right code they need to copy into their own project.
If you would like to publish your package, you can use this template I created as an example structure. Let me know if I can do anything to help!


test(rebuild): disable test

Disable the rebuild_dst_disconnect test. This test is occasionally
failing on CI/CD even with a suitably high timeout time. When this
occurs an error message is output indicating that we failed to get IO
channel because we were probably low on memory.
A ticket will be raised to investigate this fully and re-enable the
test.

Maybe comment why it is disabled, in the source code?

I thought it would be sufficient to include the reasoning in the commit message as we would probably be looking at that anyway when we come to re-enable it.

Maybe comment why it is disabled, in the source code?

I thought it would be sufficient to include the reasoning in the commit message as we would probably be looking at that anyway when we come to re-enable it.

bors merge

bors merge