add example of prior averaging such as elastic net

For Hastie et al.'s elastic net, see:
http://ba.stat.cmu.edu/journal/2010/vol05/issue01/lin.pdf
http://www.stanford.edu/~hastie/TALKS/enet_talk.pdf
Poole and Raftery also did this in a demographic modeling context:
http://www.stat.washington.edu/~raftery/Research/PDF/poole2000.pdf

Would you want a contributed example for this? I have a stan implementation of the 'Bayesian elastic net' in Li & Lin (BA 2010), but with hyperpriors on the regularization penalties, applied to a point process model. It would be easy enough to rewrite a minimal example as, ie. a logistic regression.
Apologies if this is not the right venue to offer.

Thanks.
If you want to add a LaTeX example to the manual, stan-dev/stan
is the right repo.  If you just want to add an example model, then
stan-dev/example-models is the right place.  If you want to
write a case study, then our web site repo is the right place,
stan-dev/stan-dev.github.io.

Bob

On Jul 22, 2016, at 4:41 PM, nspope<EMAIL_ADDRESS>wrote:
Would you want a contributed example for this? I have a stan implementation of the 'Bayesian elastic net' in Li & Lin (BA 2010), but with hyperpriors on the regularization penalties, applied to a point process model. It would be easy enough to rewrite a minimal example as, ie. a logistic regression.
Apologies if this is not the right venue to offer.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.

Already done.

Any links for the added example?

There was already an extant example in the manual
http://mc-stan.org/users/documentation/; section 31.2, page 381 in the
current version (2.17.0)
On Tue, Apr 10, 2018 at 4:13 AM, Benda Xu<EMAIL_ADDRESS>wrote:

Any links for the added example?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/stan/issues/518#issuecomment-380030569, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFgCZ2TlkBX6SrzHWyyxDJtDNYMoeKIfks5tnHeogaJpZM4BdFwG
.

--
Nathaniel S. Pope
PhD Candidate
University of Texas-Austin
<EMAIL_ADDRESS><EMAIL_ADDRESS>


Improve perf by compiling with no locking and allowing users to configure it

We were investigating a concurrent performance issue with JRuby at https://github.com/jruby/jruby/issues/3398 and after a few hours of investigation figured out that sqlite-jdbc is compiling sqlite with the default configuration of always threadsafe. Unfortunately it seems like that default mode does not treat separate database connections (to separate databases) as their own mutexes. As a result, parallel performance did not scale properly even when inserting into completely separate databases.
The fix, which is trivial, was to compile sqlite with SQLITE_THREADSAFE=0.
diff --git a/Makefile b/Makefile
index de1f1d3..31cd2d5 100644
--- a/Makefile
+++ b/Makefile
@@ -62,6 +62,7 @@ $(SQLITE_OUT)/sqlite3.o : $(SQLITE_UNPACKED)
            -DSQLITE_ENABLE_FTS3_PARENTHESIS \
            -DSQLITE_ENABLE_RTREE \
            -DSQLITE_ENABLE_STAT2 \
+           -DSQLITE_THREADSAFE=0 \
            $(SQLITE_FLAGS) \
            $(SQLITE_OUT)/sqlite3.c

Obviously this is not sufficient for the library. The full fix would be to build sqlite this way but when opening connections default to a thread-safe setup. As it turns out, sqlite can upgrade connections to be more threadsafe, but it can't downgrade them. The current configuration sets them by default to serialize all accesses.
The full doco for this is here: https://www.sqlite.org/threadsafe.html
Basically, sqlite-jdbc needs to configure the library to be thread-unsafe as a minimum, and then by default specify thread-safety when opening the connection. Users can then specify configuration parameters to open the connection as thread-unsafe (single thread access) giving them better concurrency if inserting into isolated databases.
I don't have a full patch for sqlite-jdbc, but I wanted to start the dialog now. We have a large number of JRuby users hitting sqlite via your library in heavily concurrent applications, and this would give them a better chance of having good scaling characteristics.

That's a good catch. OK. I'll create a non-thread safe version only for Win/Mac/Linux (x86, x86_64). We need to wait a contribution for the other platforms.

Uploaded a snapshot jar: https://oss.sonatype.org/content/repositories/snapshots/org/xerial/sqlite-jdbc/3.9.0-SNAPSHOT/, which is built with SQLITE_THREADSAFE=0
We also need to add a configuration method, which calls sqlite3_config(flags) function in sqlite3 to select thread-safe mode.

@headius By the way, did you try -DSQLITE_THREADSAFE=2 (multi-thread) mode? If we use SQLITE_THREADSAFE=0 (single thread) at compile-time, we cannot make it thread-safe with sqlite3_config.
If -DSQLITE_THREADSAFE=2 works efficiently, I would like to use this option.

@xerial I will give it a try on the benchmark from jruby/jruby#3398.

@xerial Unfortunately, SQLITE_THREADSAFE=2 seems to have the same issues as =1 and the default mode (which I believe is also =1). It doesn't seem right that sqlite blocks all threads regardless of what database they're connecting to, but that seems to be the case.

Thanks for testing. Then we should build multiple-versions of native libraries with different configuration options. The default should be thread safe mode, and by some configuration we need to use non thread-safe version.
A possible approach is using a JVM system property (e.g., '-Dsqlite-jdbc.threadsafe=false`), then load native library built with '-DSQLITE_THREADSAFE=0'. Do you think does it work for jruby?

A property would work but the problem with properties is making sure they get set early enough. A typical JRuby user just runs a Ruby script, which loads all the libraries needed. Those libraries would need a way to set the property such that it's picked up by the driver.
Can we make it a parameter of the connection?

Once the native code is loaded by JVM, we have no way to unload it. So the connection parameter would work only for the first time, and in the second time we need to use the same mode (thread-safe or unsafe) with the first connection, but this behavior might be acceptable since using a different thread-safe mode in an application would not be common.

@xerial Ahh yes, I understand. I have another suggestion that may be too complex to support...two libraries.
If we had two jni libraries with different symbols and different thread-safe modes, it would simply be a matter of calling the correct one. So, two JNI interfaces, two C files, two native libraries.
I can understand if that's too much change to introduce. The property will work ok, but we'll have to document it well (somewhere in JRuby or related libraries) so people aren't constantly reporting performance bugs to us.

@xerial I think the property will be fine. My current mystery is why other Ruby implementations do not seem to have this threading bottleneck with the sqlite3-ruby gem.

I have sent an email to the sqlite-users list to ask about threadsafety and why we might be seeing serialized performance regardless of mode or database independence.

I'm reluctant to provide two types of API (because it increase the maintenance cost) , rather I would choose to prepare two types of packages: sqlite-jdbd.jar and sqlite-jdbc-singlethread.jar.

@xerial the two package approach is actually might be the best. All jars in a typical JRuby application get loaded dynamically at runtime rather than statically on a classpath.

OK. I'll tweak packaging scripts so that we can prepare two types of binaries (normal jar and single-thread one).

28 days later... :-)
Anything I can do to help you with this?

Alternatively, you could change SQLITE_DEFAULT_MEMSTATUS
https://www.sqlite.org/compile.html#default_memstatus
Inside sqlite.c, there is a comment saying:
** SQLite holds the [SQLITE_MUTEX_STATIC_MASTER] mutex when it invokes
** the xInit method, so the xInit method need not be threadsafe.  The
** xShutdown method is only called from [sqlite3_shutdown()] so it does
** not need to be threadsafe either.  For all other methods, SQLite
** holds the [SQLITE_MUTEX_STATIC_MEM] mutex as long as the
** [SQLITE_CONFIG_MEMSTATUS] configuration option is turned on (which
** it is by default) and so the methods are automatically serialized.
** However, if [SQLITE_CONFIG_MEMSTATUS] is disabled, then the other
** methods must be threadsafe or else make their own arrangements for
** serialization.

@headius
using this test https://gist.github.com/patcheng/324f50fd360bc2e3486a (based to the file from JRuby's Issue. Make it closer to I think the version you were using.
I am using stock JRuby <IP_ADDRESS> and sqlite-jdbc from master.

I think that commit a6a559e is bogus. If multiple connections are created to the same database file, the database may get corrupted if SQLite has been compiled with -DSQLITE_THREADSAFE=0.
I propose to use -DSQLITE_THREADSAFE=2, it is faster than the default and it is safe to use within sqlite-jdbc, because the native methods in NativeDB.java are declared using synchronized.

@headius My tests were performed on a MacBook Pro with Core i7 2.8 Hz. 4 real cores, and 4 hyperthreaded cores.
@mkauf I think it's safer to stick with -DSQLITE_THREADSAFE=1.  With -DSQLITE_THREADSAFE=2, accessing the same database connection from multiple threads would cause an explicit error (as oppose to slower). I ran into that when I was doing an naive implementation for the test.
When compiling SQLITE_THREADSAFE using 1 and 2 , the behavior can be modified at run-time by specifying SQLITE_OPEN_FULLMUTEX flag in sqlite3_open_v2().  see https://www.sqlite.org/threadsafe.html

What's the status of this? It looks like either mode 1 or 2 will work with SQLITE_DEFAULT_MEMSTATUS=0, but I don't know what that flag does. If we can go with a single binary, that's obviously best, so it's probably ok to go with SQLITE_THREADSAFE=1 and memstatus=0?

@xerial We are still getting reports of slow performance on JRuby, and would really like to help you get this out. It sounds like @patcheng has come up with the right magic for safe speed and configurable behavior at runtime. What can I do to help you get a release out with these changes?

@patcheng Can you turn your changes into a PR? I'd like to see the full patch and have some of our users test it out.

@patcheng Nevermind, I realized it was trivial :-)
diff --git a/Makefile b/Makefile
index de1f1d3..df440a4 100644
--- a/Makefile
+++ b/Makefile
@@ -62,6 +62,8 @@ $(SQLITE_OUT)/sqlite3.o : $(SQLITE_UNPACKED)
            -DSQLITE_ENABLE_FTS3_PARENTHESIS \
            -DSQLITE_ENABLE_RTREE \
            -DSQLITE_ENABLE_STAT2 \
+           -DSQLITE_THREADSAFE=1 \
+           -DSQLITE_DEFAULT_MEMSTATUS=0 \
            $(SQLITE_FLAGS) \
            $(SQLITE_OUT)/sqlite3.c

@chuckremes Maybe you could build the driver with this patch and see how perf looks for you? I'd like to put this one to bed.

@headius I will try to do so today.
All I can say is "wow" when looking at all the followup you have performed on this issue since Oct 2015. Thank you very much.

Testing this patched version in a production app right now. I'll let you know what kind of performance increase I see. Last run with un-patched driver took 8 hours and 50 minutes. A good chunk of that was DB access.

Surprisingly, the latest run just finished. It took 59m 56s to complete. So this change basically shaved 8 hours off of a 9 hour run.

So this change basically shaved 8 hours off of a 9 hour run.

Well I'm convinced! How about you, @xerial?


Fix RSpec matcher for matching against already parsed JSON

@seanpdoyle I was hitting the same error mentioned in #56.
Cause
What was causing this is the following:
RSpec.describe 'Home Request Spec', type: :request do
    describe "GET /homes/:id" do
        it 'returns a single agent' do
          get "/homes/1"
          expect(response.status).to eql(200)

          payload = JSON.parse(response.body)
          expect(payload).to match_response_schema('home')
          expect(payload['id']).to eql(1)
          # .... more assertions
        end
      end
  end
end

Note in the above example expect(payload).to match_response_schema('home') where the payload is an already parsed JSON string (a Ruby Hash) and not a Ruby String.
When there is a schema mismatch, the RSpec matcher calls the pretty_json method on all objects involved. This in turn calls Payload.new(response) and fails when trying to turn the Ruby Hash into a JSON object.
Fixes
Obviously this was caused by a user error of passing in a already-parsed JSON payload into the matcher.
A couple solutions are:

Fail the matcher if the expectation is set against a Hash and tell them it must be a string.
Convert the Hash back to JSON calling #to_json on it.
If something is already a Hash, skip any attempt at conversion.

I would argue against option 1, as many request spec helpers do automatic JSON.parse calls when the content-type is application/json.
So I implemented option 2, but I think the 3rd option is just as good. I was implementing tests and then saw #57 pending and figured it was better to hold off.

@jsmestad is this already supported? The way I understand your use case appears to not require any implementation changes.
I've opened https://github.com/thoughtbot/json_matchers/pull/59 to add test coverage. Could you review that and give some feedback?


wait_for kops rolling-update

This is in response to an intermittent failure in :kops_rolling_update, "Unable to reach the kubernetes API." E.g. in https://gitlab.com/gpii-ops/gpii-infra/-/jobs/84470317.
I didn't test this very much, but I think it's safe. kops rolling-update seems to be reasonably idempotent even in the face of several failure modes.

LGTM

LGTM


Allow dynamic method calls for FactoryBot objects in Cypress

Cypress API changes
A first API for this was proposed in #671. This is a redesign of that API to make things more scalable and easier to use from within Cypress tests. With the changes in this PR, we are able to write something like this in Cypress tests:
FactoryBot.create("lecture", { teacher_id: this.teacher.id }).as("lecture");

cy.then(() => {
  this.lecture.call.long_title().then((res) => {
    cy.log(res);
  });
});

Call .call on any instance you've created with FactoryBot. On the resulting object, you can call any method, e.g. here long_title(). This will translate to a method call on the respective instance in the backend.You can even pass (multiple) arguments to this method, but of course this only works for primitive data types such as strings and integers and not when the function excepts a user object or other complex Rails objects.
For all supported method calls, see the respective tests under cypress/e2e/meta/factory_bot_spec.cy.js.
My plan is to merge this PR into dev, then remove the first proposal API from #671, then merge dev into #671 and use the new API there for the tests. This also makes PR #671 smaller.
Off-topic

In Cypress, we can now create multiple users of the same role, e.g. multiple generic users. This is achieved by adding a random hash to their email such that there is no duplicate key.

For reviewers

It's not worth to browse through my commits here as it's only in the last ones that everything works. Before that, I experimented a lot.
Convention in JS: methods that should be considered private start with a #.
There is a lot of "JavaScript magic" going on here. In order to understand the mechanism with a simpler example, read through my question here. The answers to this questions were the reason I introduced the .call syntax instead of allowing dynamic method calls directly on the resulting object. The function defined in the StackOverflow question is very similar to the final one in this PR, namely #allowDynamicMethods() of the factorybot.js. Setting the .call property is done in #defineCallProperty().
In the code here, the complexity increases because of how Cypress handles things in the .as() and .then() methods with its own wrapping mechanisms. This is handled in #createProxy().
To see how multiple arguments could be handled, see this commit. You might want to check out one commit before that to test it locally, i.e. git checkout f20d8120dc.

Out of scope

[ ] This PR also refactors the create() method of the Rails FactoriesController according to some changes already done in #671, e.g. we introduce the method validate_factory_name.
[ ] Do we also want to keep the transform_hash method? Could it still be useful? If yes, could you please add a docstring explaining what it does, e.g. input/output as I'm not too sure 😅

@fosterfarrell9 Thanks for your review, I've incorporated all your suggestions. Please take note of the "off-topic" section I've introduced in the PR comment.


Rule to handle errors

First of all, let me thank you for the great work on this tool! I use it with joy everyday. However, there are a few small annoyances that I have with it and this is the major one, for which I haven't found a decent work-around.
I'm currently writing my thesis, which is quite a complicated document such that if I make a syntax error, this introduces errors in my AUX file and hence every subsequent compilation fails even if my TeX files are all fine again.
Concretely, I would love to see a conditional pragma like arara: clean {...} if error that executes only if one of the previous rules fails.
My current work-around for this is to have the following in my main file:
%% arara: clean: {...}
% arara: xelatex
% arara: ...

when an error happens, I temporarily remove one of the % signs, hit "Build" and replace it again to avoid that I have huge compilation times afterwards.
Practically, I think something like
% arara: xelatex
% arara: ...
% arara: clean: {} if error

would be a great alternative for me.
If somebody knows an alternative (that works on arara 3, preferably), that would be great as well!

With 4.0 it is possible to search in files for error messages, so you could do something along the lines of
% arara: clean: { files: [document.aux] }
% arara: --> if found('log', '==> Fatal error occurred')

% arara: pdflatex

(for me this feature was the reason to switch to 4.0)

@samcarter8 Thank you for the hint! I will have a look at arara 4.0 (unfortunately, MacTeX still comes with 3.0).

Dear Egon,
Thank you very much for the kind words, I am very happy to hear arara is useful for you. :wink:
First and foremost, I need to apologize for the huge delay in finally releasing the new version in the wild. Time is quite complicated for me at the moment, as I need to write my thesis. The current official release (3.0) has a lot of nuisances and critical bugs that were hopefully zapped in the upcoming version (4.0).
The new version has several improvements and new features, and mostly because of them, the new manual has to be rewritten entirely, from scratch. Sadly, for me, writing manuals take a huge amount of time and effort, as I am not a native speaker. Besides, I need to write a gentle introduction to all features, as TeX users have several spectra of knowledge and might not grasp the ideas at first.
As @samcarter8 suggested, this directive conditional might indeed help you. Note that the if conditional only executes the directive (in this case, clean) if, and only if, the logical expression holds true. So, if the ==> Fatal error occurred text pattern is found in the log file, the clean directive will be triggered. Very clever!
The code is now (to some extent) frozen, but the rules are still subject to change. There is a lot of things I still want to include in them, but as they are now, I think they already offer some neat playground.  If you want, I can provide a binary of version 4.0 for you to play if (together with the new rules), so you use these new features. But I understand this might not be the best time of drastically changing workflows (your thesis, after all, comes first). :wink:
Please, let me know if you need any further help or more detailed explanations. Also, @samcarter8, thank you for the help. :wink:
All the best!
Paulo

Hi Paulo,
All my respect for the thesis coming first :+1:. To quote Douglas Adams:time is an illusion, lunchtime thesis time doubly so.
If you do have a binary for OS X, that would be very welcome since I can't seem to get maven running on homebrew (and I don't want to sink too much time into that right now).
Thanks!
PS: Maybe after both of us finish writing, we should have a chat about arara and whether I can help out a bit with documentation/coding/...

Gentle ping for @cereda: If you do have some binary available for arara 4.0, I am still very interested.


Load Network

Load a network using the network map #15 and a native file chooser.

[x] Limit the file path to the folder where the network maps are saved by default.
[x] Limit the selection of files to be in JSON format

This issue has been solved. The output of the solution is displayed below:


S-adenosyl homocysteine  parentage

Hello,
Should S-adenosyl homocysteine be an amino-acid derivative rather than amino acid?
See
https://github.com/geneontology/go-ontology/issues/12925
For further info.
Many thanks,
Val

Hi,
I have created the class 'homocysteine derivatives' (CHEBI:136505) and made it a parent term for S-adenosyl homocysteine.  This will lead to 'amino-acid derivative'.
Kind regards,
Steve

thanks!


Filter Unit-tests and Documentation

Presently, call graph generation using cflow includes C source and headers files related to unit test, documentation, and other non-production FFmpeg features. By excluding these files we could reduce noise in the call graph.
A first step to filtering such files is to identify non-production code in the FFmpeg source code repository and ensure these files are excluded by cflow.

cflow -b -r ``find -name "*.c" -or -name "*.h" | grep -vwE "(tests|doc)" works. The list of files and/or directories to ignore could be added to grep's regular expression


Publish it on F-droid

This app is pure geniality; I'm totally enjoying Houseclub with the better device the majority of iOS users with poor iPhones using Clubhouse 👍👍👍
I am trying to spread it out into my community, but I think it will be worth it to publish it on F-droid market. It has a tradition of unofficial clients as Faceslim or Newpipe so I expect a lot of its user's searches there for Clubhouse unofficial client.

Where can I download this app?

Hi, I don't know what steps to be done to use the code published here, I am not that much of a coder, can you please help on how to get Clubhouse to work on my android system?
Thanks in advance...

@hejny
F Droid seems like a great way to spread the word. Can you just publish the .apk on it or are there additional steps?

Honestly I do not know. I am a web developer not Android. But F-droid is mine favourite choose between Android markets. And I suppose for lot of dev and open source lovers too.

Wanna invite for clubhouse 🤷♂

The first thing I did is to try to look at it a F-Droid. It would be nice to have it there.

The first thing I did is to try to look at it a F-Droid. It would be nice to have it there.
Is this .apk safe in the meanwhile?
https://www.apkmirror.com/apk/grishka/houseclub/houseclub-1-0-7-release/houseclub-1-0-7-android-apk-download/

You can just download the apk from this repo release section
https://github.com/grishka/Houseclub/releases

The latest version is 1.8
Apkmirror link is not the latest version
On Sat, Feb 27, 2021, 1:36 AM Mohamed Elashri<EMAIL_ADDRESS>wrote:

The first thing I did is to try to look at it a F-Droid. It would be nice
to have it there.
Is this .apk safe in the meanwhile?
https://www.apkmirror.com/apk/grishka/houseclub/houseclub-1-0-7-release/houseclub-1-0-7-android-apk-download/
You can just download the apk from this repo release section
https://github.com/grishka/Houseclub/releases
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/grishka/Houseclub/issues/56#issuecomment-787015565,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APA24BQH3CT3QPJ7ZQG5P3TTBCHIHANCNFSM4X65OAZQ
.

Ah, hey. F-Droid contributor here. Would nice if @grishka could establish fastlane metadata which are basic metadata text files mostly used for F-Droid.


Redirect all error related messages to stderr

Is your feature request related to a problem? Please describe.
Currently, oasdiff only displays exit codes into stderr, which makes it difficult for automation scripts to gather all the displayed information about an error. Furthermore, from a CLI perspective, error messages are expected to be redirected to stderr.

Source

Describe the solution you'd like
The details in the error (example) should also be redirected to stderr:
failed to load base spec from "openapi_prod.yaml" with openapi_prod.yaml: no such file or directory
Command failed: process encountered problem: exit code 102

Describe alternatives you've considered
Redirect stdout to a file and check if the command threw an error, if so, cat the stdout and assume it is the error details.
Additional context
If we agree this is a good feature to be implemented, I'm happy to discuss further and come up with a PR to contribute and help improve oasdiff error handling.

I suggest to use logger like logrus
This way we can add functionally like setting the output and print timestamp as part of the the log

@effoeffi great suggestion, I can do an experiment PR to see what it would look like.


First hot reload does too much reloading

The first hot reload after a Run/Debug does a bunch of reloading even if you don't change anything in-between starting the app and reloading:
Reloaded in 1474ms.
Reloaded 389 of 405 libraries.

This issue occurs on Android simulator, but not iOS simulator.
Overall, this is a confusing user experience, and I'm concerned it can contribute to developers building a lack of trust in the robustness of hot reload, and for that reason would be great to fix.

Context here:
In the past we had the loader and when a Flutter application booted up the loader would be displayed until all the sources are copied. After this the loader would be killed and the application would be launched from sources on the device.
Having a loader was slower and ugly. Developers would have to wait seconds (!) before their application would appear on the device.
In order to kill the loader, I made the VM capable of reloading on top of a script snapshot. So the application would run immediately from a script snapshot and then on the first reload we would use the sources on the device.
When switching from the snapshot to the sources we can't know what has changed and have to assume everything is dirty, and we end up reloading all of the program's libraries (405 - 389 = 16 dart: libraries).
The obvious way to fix this bug is to bring the loader back, that will make the first reload only reload changed libraries.
We probably don't want to bring the loader back so we need a better way of knowing which sources files were changed after the script snapshot was generated (both of these happen on the host system). This is racy and difficult to get precise. If we think a library hasn't changed when it has the program can get into a weird state.
A workable solution: Flutter tools can timestamp all sources files fed into the script snapshot and then maintain the set of files that have changed since then. This set would need to be passed to the VM on the first reload.

How much of this work can we do on the device while the app is running? Could we wait for the first few seconds of idleness on the device and do it then, silently?

@Hixie The issue there is that at the moment we do the auto-initial-reload we may have bad/weird sources and we break the application. We might be able to get the VM to extract the script snapshot sources onto the disk in the same layout as DevFS will use and then reload from the extracted sources (known good enough to get the app running)

Fair enough.
In that case I suggest that for the first hot reload, we replace the message with "Initialising hot reload subsystem, please stand by...", to set the right expectations.

https://github.com/flutter/flutter/pull/9418
^--- changes the message.

Moving to M4 now that we have a better message in the tool.

This will get fixed when we switch to using the new front end. The workflow is a bit different whenusing the new pipeline, the app is incrementally compiled on the host and the resulting kernel file is pushed to the device. The engine then reloads this new incremental kernel file. So this notion of treating all source files as new after they are pushed to the device will not be there.
(assigning this bug to @aam as he has wired the new pipeline path for hot reload).

Great news, thanks :-)

Is there still work to do? #13699 was merged a year ago.

Closing this issue as we have migrated to Dart 2.


One's innermost thoughts and feelings

You are good, boy. You are my pride!

Eeee, eeee EE eeeee? Eeeeee, eeee, eeeeee!


Use trigger first in ordinal

I noticed that when a description contained the trigger for a different
snippet, the snippet with the description would be sorted before the
snippet with the matching trigger.
before:

after:

Thank you very much! I knew something wasn't quite right, but the penny hadn't dropped for me!
Looks good 👍


React HMR bug - doesn't reload storybook iframe

Hello!
Minimal bug reproduction repo: https://github.com/sukazavr/storybook-builder-vite-hmr
I face unexpected behavior:

Run command npm run sb
In storybook open Button / Primary story
Try to change file src/Button/Button.tsx
It doesn't update component in opened story, it requires manual iframe refreshment
This affects every story, you can try to change src/modules/app/App.tsx

What I noticed:

CSS changes work as expected -- instant update in story
Story file updates work as expected
Passing fastRefresh: true in react plugin doesn't fix the issue
Experiments with storybook configs were fruitless
Vite in dev mode (w/o Storybook) works as expected

Please help me, I'm deadlocked 🤷♂

I'm not able to reproduce using your repo.  I've installed packages with npm, run npm run sb, changed the button label, and when I save the change appears instantly with HMR.  Maybe you have some bad state locally?  Or, a browser extension is causing issues?

Ian thank you very much for checking!
It turned out that it was AdGuard black magic filtration 😭
I tried so many things but hadn't thought about a different layer where is the issue.


[NT-205] Manage pledge reward section

📲 What

Adds the backed reward to the ManagePledge screen

🤔 Why

To allow users to see which reward they chose.

🛠 How

By creating a ManagePledgeRewardView containing basically the RewardCardView and a title label.
The RewardCardView now needs RewardCardViewContext to be configured properly, since little UI changes will occur depending if the reward is being seen from the Rewards Carousel or from the ManagePledgeViewController
Now that ManagePledgeViewController contains all the sections, snapshots were added

Note:
The No Reward title wasn't updated. This will be made in a small PR (coming soon) to avoid this PR to get too big.
👀 See
Trello, screenshots, external resources?

Default 🐛
Dynamic Type 🦋

♿ Accessibility

[ ] Works with VoiceOver
[ ] Supports Dynamic Type

✅ Acceptance criteria

[ ] The backed reward should be shown on the ManagePledge screen below Payment Methods section.
[ ] The section title label  should show Selected reward

By accident I've noticed this weirdness...any idea what's going on in there?? 🤔


How to limit colors used

Certain colors like dark red and dark green don't go together. Is there a way to limit or change the color options? If not, can you point me to the code loation where I can change that?
thank you for open sourcing this.

Yes, you can fork it and update the /src/blockies.ts, but if you did, it would be against native logic (https://github.com/download13/blockies)

k, thanks.


Fixes a few broken links

This fixes a few broken RogueBasin links that I noticed during my 7DRL.
I also tried building the project using make all but it ended up with a lot of differences that appeared not to affect anything but would probably make this harder to review. The results are here. I'm happy to have that be the PR instead if that's easier, but I'm likely doing something wrong with my build process, or some backing libraries have updated and now there is not a need for the _partial prefixing anymore.
I'm happy to document the build process if that would be useful, but I'm not sure how to get it compiled and working.

Hi @katerberg,
thanks for your PR! I will merge this right now.
The rebuild issue is probably caused by some newer ts/minification tool version; I would not really care about that. Your changes have value w.r.t. documentation, so the code probably does not need to get rebuild at all.


Minio permission check solution

          Another option:

Create a pair of access_key & access_secret for each bucket(namespace)

Only have read/write permission to that bucket

Use the above access_key & access_secret to create a datasource for each namespace

Then when user upload files ,it :

get the datasource  from the namespace
use the access_key & access_secret to upload files

The above solutions brings a new problem:

when and how to create the access_key * access_secret

Originally posted by @bjwswang in https://github.com/kubeagi/arcadia/pull/284#discussion_r1403794390

Another benefit if we use Datasource to authorize users to manage bucket is :

User can use this datasource(accesskey&access secret)  to upload files with mc

github.com/minio/madmin-go/v3
mac, err := madmin.NewWithOptions(endpoint, &madmin.Options{
		Creds:  credentials.NewStaticV4(username, password, ""),
		Secure: false,
	})
	if err != nil {
		panic(err)
	}
	policy := `{
		"Version": "2012-10-17",
		"Statement": [
		 {
		  "Effect": "Allow",
		  "Action": [
		   "s3:*"
		  ],
		  "Resource": [
		   "arn:aws:s3:::abc/**"
		  ]
		 }
		]
	   }`
	result, err := mac.AddServiceAccount(context.TODO(), madmin.AddServiceAccountReq{
		Policy: []byte(policy),
	})

Seems that do permission check on relevant CRDs is more simple.

Route changes to file upload

/versioneddataset/files
/model/files

Done with cani solution


Reorganize the CLI structure ?

I propose to reorganize the CLI structure, there are not many functions yet.
it would be wise to store commands in the map
import './commands/init/init.dart';
import './commands/create/project/project.dart';
import './commands/create/page/page.dart';
import './commands/create/view/view.dart';
import './commands/generate/locales/locales.dart';
import './commands/install/install.dart';
import './commands/version/version.dart';

const commands = {
  'init': initCommand,
  'create': {
    'project': createProjectCommand,
    'page': createPageCommand,
    'view': createViewCommand,
    ...
  },
  'generate': {
    'locales': generateLocalesCommand,
    ...
  },
  'install': installCommand,
  '-v', versionCommand, // change to `version`, to have the same structure everywhere?
  '-version', versionCommand, // and remove this alias?
  ...
};

// map for help in console
const hints = {
  'init': 'generate the chosen structure on an existing project',
  'create': {
    'project': 'create a flutter project in the current directory',
    ...
  },
  ...
};

running the command can generate multiple files
./commands/create/page/samples/controller.dart
./commands/create/page/samples/binding.dart
./commands/create/page/samples/view.dart

Motivation:

All commands have one clear structure.
To add a new command, you need to create a separate independent directory.
Easily generate help in the console.
It is easy to check that the command exists and at this nesting level is a function.
Easy to expand functionality name unlimited command nesting.

Commands should extend the abstract class, which is a generator and requires the implementation of the necessary functionality.

Over the weekend I will work on it

I'm currently a little busy with other tasks

maybe something similar?
i can help migrate existing features over the weekend
abstract class Command {
  /// hint for console
  String get hint;

  /// validate command line arguments
  bool validate();

  /// execute command
  Future<void> execute();
}

class ExampleCommand extends Command {
  String get hint => throw UnimplementedError();

  @override
  bool validate() {
    // TODO: implement validate
    throw UnimplementedError();
  }

  @override
  Future<void> execute() {
    // TODO: implement execute
    throw UnimplementedError();
  }
}

void main() {
  final commands = {
    'create': {
      'example': () => ExampleCommand(),
    }
  };

  final hints = {
    'create': {
      'example': ExampleCommand().hint,
    }
  };

  // find command by arguments
  final command = commands['...']['...']();

  // print errors
  if (command.validate()) {
    command.execute();
  }
}

I am very grateful for your help

@CpdnCristiano I have implemented the api I suggested. Where can I show an idea? this is from a clean project

if you want you can create a repository on github

https://github.com/alexkharech/get_cli_new_api

very good, I liked it a lot I will implement it as soon as possible

implemented some of your tips


Clarification on ORTB2, FPD and Content Categories v3

In this document: https://docs.prebid.org/features/firstPartyData.html
We see cat, sectioncat and pagecat under the ortb2, site section.  The format of the values in those keys is listed in this IAB document: https://www.iab.com/wp-content/uploads/2016/03/OpenRTB-API-Specification-Version-2-5-FINAL.pdf
In the linked OpenRTB2.5 spec cat/sectioncat/pagecat values are mentioned in section 3.2.13 and the table of values is in section 5 .1 "Enumerated Lists Specifications, Content Categories".
That IAB document is from 2016 and the categorizations in the code example appear to be from the now-deprecated Content Categories v1.0.
Can we use the content categories from the more-current Content Categories v3 (https://iabtechlab.com/wp-content/uploads/2023/03/Content-Taxonomy-v3.0-FINAL.xlsx)?  If so, what does that look like syntactically?

Hi @nibuca
The contextual signals are a bit confusing. I try to summarize what I think is the current state of things 😅

cat, sectioncat and pagecat are and always will contain the values from the OpenRTB 2.5 spec mentioned in section 3.2.13 as you pointed out. The example in the supplying global data section uses these values:

cat: ["IAB2"],
sectioncat: ["IAB2-2"],
pagecat: ["IAB2-2"],

The new Content Categories v3 have a new place in the OpenRTB object under site.content.data. The containing object has a property ext.segtax, which contains the taxonomy version. See https://github.com/InteractiveAdvertisingBureau/openrtb/blob/master/extensions/community_extensions/segtax.md

Can we use the content categories from the more-current Content Categories v3

Not in the site.cat, etc. properties. Taking the example from the prebid page
pbjs.setConfig({
  ortb2: {
    site: {
      // this can only be OpenRTB 2.5 / Content Taxonomy
      cat: ["IAB2"],
      sectioncat: ["IAB2-2"],
      pagecat: ["IAB2-2"],

      // this is where the contextual data is placed
      content: {
        data: [
          {
            // I think this will help SSPs/DSPs to validate where the data is coming from
            name: "www.dataprovider1.com",
            ext: {
              // this is the new standard to define which taxonomy is used in the segments array
              segtax: 7,
            },
            // the bare minimum are the IDs. These IDs are the ones from the new IAB Content Taxonomy v3
            segment: [{ id: "687" }, { id: "123" }],
          },
          {
            /* ... more data ... */
          },
        ],
      },
    },
  },
});

Thank you for the annotated response.  This is very helpful.


Ignore binaries and honor .gitignore

Is your feature request related to a problem? Please describe.
I'm running comby on a big project with lots of build files stored in the same tree as the git repository (ignored by .gitignore). Additionally we also have a lot of binary files actually committed to the repository.
The build files are autogenerated sources as well as binary build products.
Describe the solution you'd like
It would be great to have comby ignore all files ignored by git and also binary files.
One reason I use ripgrep is because it does exactly this, which makes it orders of magnitude faster than simple grep. See: https://github.com/BurntSushi/ripgrep/blob/master/GUIDE.md#automatic-filtering
Additional context
Luckily there was a timeout message that made me aware it's searching binaries:
> ./comby  'failUnlessEqual(:[a],:[b])' 'assertEqual(:[a],:[b])'
Timeout for input: Path: /home/zoid/cloudhome/hpe/taiwan/edk2/comby!
Timeout for input: Path: /home/zoid/cloudhome/hpe/taiwan/edk2/Build/FreedomU540HiFiveUnleashed/DEBUG_GCC5/FV/U540.fd!
Timeout for input: Path: /home/zoid/cloudhome/hpe/taiwan/edk2/Build/FreedomU540HiFiveUnleashed/DEBUG_GCC5/FV/DXEFV.Fv!
Timeout for input: Path: /home/zoid/cloudhome/hpe/taiwan/edk2/Build/FreedomU540HiFiveUnleashed/DEBUG_GCC5/FV/Ffs/9E21FD93-9C72-4c15-8C4B-E77F1DB2D792FVMAIN_COMPACT/9E21FD93-9C72-4c15-8C4B-E77F1DB2D792SEC1.guided.dummy!
Timeout for input: Path: /home/zoid/cloudhome/hpe/taiwan/edk2/Build/FreedomU540HiFiveUnleashed/DEBUG_GCC5/FV/Ffs/9E21FD93-9C72-4c15-8C4B-E77F1DB2D792FVMAIN_COMPACT/9E21FD93-9C72-4c15-8C4B-E77F1DB2D792SEC1.1fv.sec!
Timeout for input: Path: /home/zoid/cloudhome/hpe/taiwan/edk2/Build/FreedomU540HiFiveUnleashed/DEBUG_GCC5/RISCV64/DxeCore.debug!

Do I understand it correctly that it also means that a comby process dies and files that would have been subsequently processed by it are ignored? Because I see this behavior and the same kind of timeouts.

Do I understand it correctly that it also means that a comby process dies and files that would have been subsequently processed by it are ignored?

It shouldn't be that the process dies. Certainly if a file times out it is skipped.
I'll look into addressing this soon, in the mean time, interim solution you might find useful:
You can use a -rg flag with comby where ripgrep will preprocess the files to search based on some criteria. This means that ripgrep could to some extent currently do the job of honoring the .gitignore file and skipping binary files. You must have ripgrep i.e., rg installed on your PATH. Here are some example invocations:

comby 'change(:[1])' 'me' -matcher .go -rg ""

Underneath the hood, rg is invoked to find files that that will match the input pattern, and honor .gitignore and binary ignores

comby 'change(:[1])' 'me' -matcher .go -rg "-g '*.go'"

Underneath the hood, rg is invoked to match files that honor the -g '*.go' glob pattern. The inside single quotes are significant here. Be aware that adding -g in rg effectively turns off honoring the .gitignore.

LIMITATIONS

You cannot invoke something like comby 'change(:[1])' 'me' custom.txt -matcher .go -rg "" and expect only custom.txt files to match, the rg invocation takes precedence and will match all candidate files. To only match a custom.txt, it is best to specify a file match pattern that expresses this.

Note that even rg will not honor .gitignore files when an explicit file pattern is provided. I.e., rg will not honor the .gitignore in the following cases, it is turned off:

rg -g '*.txt' pattern - this will search all *.txt files, even if they are listed in the .gitignore file
rg find-me * - this will search all files, including those listed in the .gitignore file.

In this sense, comby is the same, and will likely stay the same. The part that I will add is that the .gitignore is honored in absence of an explicit file path pattern. And ignoring the binary files :-)

Thank you @rvantonder for the prompt reply – the -rg "" options works well – things are fast and there are no timeouts.
But now as I tested it, I see the same outcome - still just one arbitrary & non-deterministic file gets replaced (instead of 8).

It shouldn't be that the process dies. Certainly if a file times out it is skipped.

So it seems like what you said 👆 holds – the skipped files and warnings about timeouts are unrelated.
Since the misses files are not related to the original problem reported in this issue, let's follow up on it offline?

For others who may come across this issue – my problem was totally unrelated to binary file timeouts, and was solved by providing the -matcher .txt option (as I wanted to do a simple literal replacement)

https://github.com/comby-tools/comby/issues/237#issuecomment-821468963 this method works exceptionally well. my search time down from several minutes to just a second. finally I get blazingly fast comby even on a three millions LoC codebase!


Change encoders and uint128/256

@NicolasDorier, this PR contains changes in:
Encoders

EncodeData method signature changed. Basically, every time we deal with arrays we can see the same pattern all around the .NET libraries: (byte[] data, int offset, int count). That pattern is correct and flexible.

string EncodeData(byte[] data, int length)  // old version
string EncodeData(byte[] data, int offset, int count) // new version

ASCIIEncoder
New implementation uses the .NET Encoding.ASCII class ( GetString / GetBytes methods)
Base58Encoder
New implementation uses Buffer.BlockCopy to manipulate (extract/concat) arrays of bytes instead of Linq. I performed a simple test and the improvement in performance is good (31ms encoding 10 arrays[40])
Base64Encoder
Tiny change (only the method signature)
HexEncoder
I simplified the encoding code using a lookup table what made it easier to understand/mantain and it performs very well. I didn't measured it. However, given it uses a lookup table, it should perform better than the previous algorithm.
unit128 / uint256
I refactored them in order to eliminate duplicated code. Also, all byte-per-byte operations were replaced by uint32 operations (simplicity and performance). As a result, these classes are ~50% smaller than before.
Others

I fixed a broken test. It wasn't failing but it wasn't really testing neither.

Tests
All existing tests are green.

I will test that.
However, I don't want to use the StringBuilder. I did in the past, but since EncodeData is often used, I runned into performance and memory problems which resulted into a very busy GC.

Ok, don't worry about the StringBuilder issue, I can test the performance/memory behaiour and a make a benchmark for both the original and the new implementations if you want.

for the StringBuilder part ? you can do it, but I am very sure about what I am saying.

np. I've removed the StringBuilder. The resulting algorithm looks very very similar to the previous one but I think it is an improvement because the original was O(n^2) and the new one is O(n).
That is because IsDigit() uses an IndexOf twice for each byte.

Not sure I understand what you mean, commit 2a3daff7 was using a StringBuilder initially, as far as I can see, as you are doing. I don't see it is O(n^2)

IsDigit uses IndexOf that is O(n/2).
IsDigit is invoked twice for each byte: 2n O(n/2) = O(n^2)


Event parsing into enums sometimes too strict?

Hi,
I was porting inputplug-rust to 0.7.0 and found that while some code has been simplified by the new parsing code, not everything works as it did before. XInput Events like XISlaveRemoved return 0 as the type, so I had a piece of code to handle that:
if self.type_ == 0 {
    "".to_string()
} else {
    format!("XI{:?}", DeviceType::try_from(self.type_).unwrap_or_else(|_| {
        panic!("Unknown device type: {}", self.type_);
    }))
},

which made this output possible:
X Input extension opcode: 131
"/bin/true" "XISlaveAdded" "14" "XIFloatingSlave" "Logitech M325"
"/bin/true" "XIDeviceEnabled" "14" "XISlavePointer" "Logitech M325"
"/bin/true" "XIDeviceDisabled" "14" "XISlavePointer" ""
"/bin/true" "XISlaveRemoved" "14" "" ""

Now, I’m getting this:
X Input extension opcode: 131
"/bin/true" "XISlaveAdded" "14" "XIFloatingSlave" "Logitech M325"
"/bin/true" "XIDeviceEnabled" "14" "XISlavePointer" "Logitech M325"
"/bin/true" "XIDeviceDisabled" "14" "XISlavePointer" ""
Error: Failed to get an event

Caused by:
    A value could not be parsed into an enumeration

If you’re curious about the code, here’s the commit:
andrewshadura/inputplug-rust@897f1fcc5799f993db6e96a33962dda6cee15731

Duplicate of #458, I think. At least that issue is also about the server sending invalid data (according to the XInput spec).
If you agree that this is a duplicate, then please close the issue.
Upstream bug report for "stop sending invalid data" is at https://gitlab.freedesktop.org/xorg/xserver/-/issues/1036.
Patch to xcb-proto to add this invalid stuff to the XML is at https://gitlab.freedesktop.org/xorg/proto/xcbproto/-/merge_requests/13.
If you are interested in some (only half-helpful) work around, then my suggestion would be to use wait_for_raw_event() instead of wait_for_event() (there are also raw versions of other APIs). These then give you the moral equivalent of Vec<u8> instead of a parsed event. You can then try parsing those raw bytes via conn.parse_event(event.as_ref()).

This allows you to handle "failed to parse an event" specially (dunno if that is worth it; you could also match on the error that is returned)
This allows you to come up with some other parsing strategy for these events. I have no good suggestions. Bad suggestions would be to use the xcb crate (which means transmuteing the event to the right type, but there is some API in xcb to hide the transmute (uhm... does xcb support xinput? I'm not sure)).

Sorry, these are all my current ideas.

Hi,

Duplicate of #458 https://github.com/psychon/x11rb/issues/458, I think. At least that issue is also about the server sending invalid data (according to the XInput spec).

If you agree that this is a duplicate, then please close the issue.

You appear to be right, it's even the same part of the spec.

If you are interested in some (only half-helpful) work around, then my suggestion would be to use wait_for_raw_event() instead of wait_for_event() (there are also raw versions of other APIs). These then give you the moral equivalent of Vec<u8> instead of a parsed event. You can then try parsing those raw bytes via conn.parse_event(event.as_ref()).

I'm afraid that's what I'll have to do. As far as I can see, that is the interface I used to use in <0.5.
--
Cheers,
Andrej

Right, it turns out while I can use it, try_from() will still attempt to parse the enums and fail, giving me an Err.

Yeah, sorry. You would have to define your own version of the struct in question, which needs a big copy&paste of the code and then replacing the enum member with an u[correct size]. Sorry for not being clearer here before.


seaweedfs: 2.24 -> 2.26

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/chrislusf/seaweedfs/releases.
meta.description for seaweedfs is: "Simple and highly scalable distributed file system"
meta.homepage for seaweedfs is: "https://github.com/chrislusf/seaweedfs"
meta.changelog for seaweedfs is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 2.26 with grep in /nix/store/ffc1nc1nbx3i1hs8m5fgv4mn4asxcswv-seaweedfs-2.26

directory tree listing: https://gist.github.com/815acbb823670836a130e09c202f5c0d

du listing: https://gist.github.com/5f549383927686080802986b77a1a30b

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
seaweedfs

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ffc1nc1nbx3i1hs8m5fgv4mn4asxcswv-seaweedfs-2.26 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A seaweedfs https://github.com/r-ryantm/nixpkgs/archive/847274a7655cf290e5238fe35198ec1ab826c616.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ffc1nc1nbx3i1hs8m5fgv4mn4asxcswv-seaweedfs-2.26
ls -la /nix/store/ffc1nc1nbx3i1hs8m5fgv4mn4asxcswv-seaweedfs-2.26/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

seaweedfs

Maintainer pings
cc @raboof @kalbasit for testing.

Result of nixpkgs-review pr 113300 run on x86_64-linux 1

1 package built:

seaweedfs

Result of nixpkgs-review pr 113300 at 847274a7 run on aarch64-linux 1

1 package built:

seaweedfs


Demo not working

It never loads.

The demo does load, but the bundle is quite large - and hence it takes a while to get going (especially on a slower internet connection).
Will look at optimising/splitting up the bundle

@hoschi what browser were you using at the time?

Chrome Mobile on my Pixel C tablet with wifi.
rob miller<EMAIL_ADDRESS>schrieb am Sa., 29. Sep. 2018, 10:49:

@hoschi https://github.com/hoschi what browser were you using at the
time?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/BHP-DevHub/react-timeline-9000/issues/128#issuecomment-425628514,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJ9OL2Q3sEa0xHoien-E9QCtzp5BlcOks5ufzQMgaJpZM4W95KG
.

Tried it on desktop now and it works indeed, but takes really long to load.


Make sure we use the native Promise to schedule utask when they're available

Due to https://github.com/jakearchibald/es6-promise/issues/140, es6-promise would always override the global Promise in Chrome (because of a very minor bug in Chrome).
Zone would only use a Promise to schedule utask when a native implementation is present, otherwise it would fallback to other mechanism depending on the environment.
Because of es6-promise overwriting the native Promise impl in Chrome, it would use mutation observers to schedule microtasks. This PR makes sure we check/use native Promises before es6-promise as a chance to overwrite it.
/cc @IgorMinar @mhevery @jeffbcross @btford @adamdbradley
I've hit the bug while trying to update zone.js to 5.0.9 in angular2:

zone.js was using Mutation Observer,
zone.js monkey patch Mutation Observer but our impl happened to be flawed and a fix has been merged into 5.0.9
it caused my zone 0.5.9 PR to fail on Angular2 - this is also because Travis is using an old version of Chrome. Tests were green on my local machine.

Obviously this PR will most probably (to be confirmed) fix the problem in Chrome.
What is left to be tested is the behavior with a browser that has support for Mutation Observer but not for Promise (should be IE11 only).
TODO:

[ ] test this PR with IE11

I have investigated more and find the root cause - the actual issue has nothing to do with mutation observers but is related to https://github.com/angular/zone.js/commit/d44d699666c4e7c81fc56404af8f44bbaf5612e5
Declaring function inside blocks is not allowed in JS and lead to the following weird behavior in Chrome:
// not valid
if (true) {
  function test() {
    alert('if');
  }
} else {
  function test() {
    alert('else');
  }
}

test(); // "else" !!!

// valid
var test;

if (true) {
  test = function () {
    alert('if');
  }
} else {
  test = function () {
    alert('else');
  }
}

test(); // "if"

Because of this behavior, zone.js uses Symbol() to generate unique keys in 0.5.9 - in 0.5.8 it would use the version based on plain string because of the above bugs.
It turns out that Symbol are flawed on Dartium (Chrome 39.0.2171) which lead to angular.js being broken when using zone 0.5.9.

Would be good to add an integration test with es6-promsie to be sure that we do the right thing when it's present (and maybe track changes to es6-promise).

When using a string key rather than a Symbol, we should be making sure that the property we add is not enumerable.

LGTM– chatted with @vicb in person and decided to create follow-up issues for the points I raised here, since both are sort of "separate" concerns from landing this fix.

Published a release as 0.5.10


Update Identifier kind name

Move the default http identifier out of the io.l5d package.
Change the kind from default to io.l5d.default.

while where here... should we choose another name besides default?  I.e. we might change the default at some point...  Also there may be identifiers for other plugins (is it confusing to have io.l5d.default be different across protocols)?  Perhaps io.l5d.http?

let's hold off on merging backwards-incompatible changes for the moment. there appear to be some issues in 0.5.0 that we should diagnose first.

hmmm... so sorry to :bike::house: naming, but technically this is versionAndMethodAndMaybeHostAndMaybeURI...  other ideas: httpMeta, httpEnvolope...?

I feel like MethodAndHost captures the essence of the identifier even if it's not a totally complete description of everything the identifier uses.  Envelope reminds me of SOAP and meta reminds me of the html meta tag.

I guess my main quibble is that host isn't included for http/1.0 requests

:star:

⭐ 🔨  Thanks for updating.


[Issue] allow azd (via azure.yaml) to add —target to docker build

Describe the bug
Currently azure.yaml does not provide a mechanism to add a --target parameter to docker build. This is necessary for multi-stage docker build where there are multiple layers and at build time one decides which layer to target.
To Reproduce
Run azd package on a multi-stage docker file there are no options to pass the --target argument.
Expected behavior
If one were to build the docker file here's how one would pass the argument:
docker build --target foo -t docker.io/bar/baz -f foo/dockerfile .

Environment
Does not matter.

Does this already existing feature https://github.com/Azure/azure-dev/pull/2266 help achieve that? cc @vhvb1989  @wbreza

--target is a different argument than what goes in buildargs.
I started a PR here that might be enough to unblock. I don't think its complete but could be a starting point.
https://github.com/Azure/azure-dev/pull/3052


Chat and Forum links no longer open glitter/forum

Hi,
It's been a few days since I logged in.  I just logged in using the standard e-mail address.  However, now that I am logged in when I click "Chat" I get challenge one instead of opening a page with glitter.  I have already completed challenge one and it used to just open the "Chat".
Also, if I then click "Chat" again while on the challenge one page, glitter will then open.
The function is the same with forum (except brings up challenge two, once on challenge two click again and forum opens).
I just wanted to mention it, in case it wasn't intended to operate this way.
Thanks.

I'm failing to reproduce this error. Additionally, checking the source the links appear to be valid. I'm closing this issue but feel free to comment and I'll reopen if you still experience it.


Housekeeping

It's long overdue I paid more attention to this project and so this PR should provide some basic housekeeping:

[feat]: automatically publish package on merge into master branch
[fix]: blog link in the readme
[fix]: linting wasn't working on this repo
[chore]: update node-sass so this project supports node 10
[chore]: remove unused test files and dependencies
[chore]: remove unused yarn.lock file
[chore]: add stale activity detection to this repo
[chore]: update contact info in package.json

I'm hoping this will streamline future development work in this project. I'll merge this sometime next week unless there are any objections (which will be very welcome 😄)

Thanks for adding me to the project @michaelfitzhavey !
Will check if the PR has any issues with my current use cases, but all seems well.
I'm pretty new to Oppen Source, so please let me know if I am doing something wrong.
I appreciate any comment and tip on ways to improve my collaboration :blush:

@Chrisimir this is great, thanks for the webpack dev dependency fix! I'll double check this PR again this evening and then hopefully we can merge.


Error for auto scope, when no previous transaction exists

There are probably 2 bugs
https://github.com/VitexSoftware/abraflexi-raiffeisenbank/blob/4efcb4b5582e1651b9957aac14099a0a0594332d/src/AbraFlexi/RaiffeisenBank/Transactor.php#L216

'two days ago' should read '2 days ago' - parsing will fail here
intention was probably to set it to now, not 2 days ago - current line causes 'since' grater than 'until'

IMHO, when there is no previous transaction, it would worth to set last 90 days period. since = '89 days ago', until 'now'

may be I was unclear:
https://github.com/VitexSoftware/abraflexi-raiffeisenbank/blob/4efcb4b5582e1651b9957aac14099a0a0594332d/src/AbraFlexi/RaiffeisenBank/Transactor.php#L212-L217
When no previous record is found, the api query fails, because parameter "from" cannot be greater than "to". E.g. today, on 2024-02-21, "from" is set on 2024-02-20 and "to" is set on 2024-02-19.
Changing this part of code to
            ... else {
                    $this->since = (new \DateTime('89 days ago'))->setTime(0, 0);
                }
                $this->until = (new \DateTime('now'))->setTime(0, 0);
                break;

works perfectly.


Add ImageResponse?

How about adding an Zend\Diactoros\Response\ImageResponse that supports the most common file types like JPG, GIF and PNG? How could this be archieved?

I would say let Diactoros be safe from all these and only rely on the psr-7 interfaces.
If we need, we can add to Diactoros\Extras or something.
You may ask, what is the advantage ?
If we do add more helper function people will use those, and the purpose of switching between psr-7 packages will get into trouble. Lets not bring it due to the same.

@harikt
Thanks for your feedback. For the same reason then Zend\Diactoros\Response\HtmlResponse or Zend\Diactoros\Response\JsonResponse should be deleted.

I don't know that will happen due to BC break. But I think yes.

But these Reponse classes are really useful in the context of a Zend\Expressive application. If you want to remove them from Zend\Diactoros where should they be placed? Moving them to a different  Zend\Diactoros package won't really solve the problem. People will still use them.

@RalfEggert I don't know the whole edge cases, but this is what I was thinking.
Zend\Diactoros\Extras can be type hinted to psr-7 response interfaces. So that means not just diactors can use these, but also any psr-7 responses.
But I understand that is not so simple, as the current ones are doing.
return new [JsonResponse](https://github.com/zendframework/zend-diactoros/blob/master/src/Response/JsonResponse.php)();

So I don't have a real answer for the current time. But I will think about the same.

I want to keep them. I don't see how they reduce compatibility with PSR7. Those helper methods still create a PSR7 ResponseInterface. We typically only use those helper classes on controllers (which are tied to a framework like Expressive, so it definitely makes sense to use them), but on other layer we still typehint against ResponseInterface.
Those are just shortcuts that are super convenient to use. -1 for removing them.

@bakura10
I have the same opinion that they are very useful and should be kept.
But what about the Zend\Diactoros\Response\ImageResponse I suggested?

I feel we should support anything that is often required. I'm not sure about ImageResponse. What is the use case? You return an image after processing in the back-end?

This repository has been closed and moved to laminas/laminas-diactoros; a new issue has been opened at https://github.com/laminas/laminas-diactoros/issues/28.


Documentation - ipa vs. ipa (shenzhen)?

In the Readme.md, in the list of tools there is ipa listed. For me it unclear if this referes to a fastlane tool or to shenzhen.

Good point, I'll make the README clearer. It's shenzhen under the hood!

Thanks - good to know! I was searching for the fastlane "ipa" documentation and realized it was not there.


(Code) - Bugfix: Cannot call seed() with pre-declared int value.

The library used in the generated code accepts an integer.
Integers in SCT are really longs under the hood.
Consequently:
int x = 123;
seed(x);
leads to a "Cannot convert long to int" error from the compiler.

Closed in #209


uint64 to number64

Change Epoch, Shard, Slot, ValidatorIndex, genesisTime, depositIndex
to number64.
This relies on the chain module PR and the new ssz library. It won't pass tests until we upgrade ssz b/c our current version of ssz doesn't support number64 types.

This is an awesome pr i love it!
Is there even a need to call it number64?

there are a few things named number64

the typescript type - this doesn't need to be named number64, I named it this to mirror the uint64 type, but we can use something else
the ssz type variable name - this doesn't need to be named number64, but it does need to be named the same as the typescsript type (our type consistency tests make sure of this)
the ssz type variable value - this either needs to be either "number64" or {type: Type.uint, bytelength: 8, offset: 0, useNumber: true} so that ssz knows how to de/serialize it

ahhhh i gothcya, no i totally agree it does make sense! Theres some tests failing due to the changes not sure why. i can look into those if you want?

Tests are failing due to still using the old ssz, which doesn't support number64. We'll need to upgrade to the typescript rewrite to get number64 support.

Do we want to wait for SSZ?

Yeah, we should probably wait for a new ssz, so we can keep our tests passing.

@wemeetagain Unfortunately, we need to wait for npm to get back to us -- ill add you to the exisiting team and we can go from there.

@wemeetagain sooooo we got locked out of npm completely... I'm trying to get on call with them...

With an update to SSZ and a conflict fix we should be good :)

This should be good to go~


add expiration date and filtering options to offers everywhere

There are two features / enhancements which I'd like to see added to every offer table. They are already added at some points, but not everywhere:

Filtering by offer status (currently being added here):

https://github.com/kodadot/nft-gallery/pull/3564

Estimation of time to expiration of offer (added here):

https://github.com/kodadot/nft-gallery/pull/3452

Currently we're showing offers at four points:

user level
global stats level
item level
collection level

Let's make sure each of those tables is providing information about expiration of offers as well as option to filter for desired Offer status.

👋


gleeunit is not compatible with gleam_stdlib 0.24

Dependencies have diverged:

gleam_stdlib (Hex package)
the dependency gleam_stdlib in mix.exs is overriding a child dependency:

In mix.exs:
{:gleam_stdlib, "~> 0.24", [env: :prod, repo: "hexpm", hex: "gleam_stdlib", compile: "gleam build", app: false]}

In deps/gleeunit/mix.exs:
{:gleam_stdlib, "~> 0.19", [env: :prod, hex: "gleam_stdlib", repo: "hexpm", optional: false]}

Ensure they match or specify one of the above in your deps and set "override: true"
** (Mix) Can't continue due to errors on dependencies

Could you expand upon the error? I'm not familiar with what Mix is doing here.
Gleeunit is compatible with gleam_stdlib 0.24, and that error prints compatible version constraints.


Divide up talks

[x] 9:00: 30m 01-Lecture: Introduction (Nick)
[x] 9:30: 15m 02-Lecture: Basics of Go (Nathan)
[x] 9:55: 15m 03-Lecture: Types (Brett)
[x] 10:20: 15m 04-Lecture: Functions & standard library (basics) (James)
[ ] 10:45: 15m 05-Lecture: Control structures: if, switch, for (while and classic for)
[x] 11:10: 15m 06-Lecture: Pointers (Matthias)
[x] 1:00: 15m: 07-Lecture: map (Lukasz)
[x] 1:25: 15m: 08-Lecture: slices (Nathan)
[ ] 1:50: 15m: 09-Lecture: defined types, structs
[x] 2:15: 15m: 10-Lecture: Methods (James)
[x] 2:40: 15m: 11-Lecture: Interfaces (Brett)
[x] 3:05: 15m: 12-Lecture: Error (Gerrit)
[x] Introduce Capstone project + go build and local environment (Matthias)
[x] 5:00: 15m: Closing remarks (Nick)

@nathany are you interested in doing a second one?
I don't have Lucasz, but he should get a pick as well.

@matthias-stone: Error and/or User-defined types, structs, or map would be of interest.

@boersn This is a research paper on Go & Swift. You may find some good references for the intro talk. https://github.com/jakerockland/go-vs-swift
I would like a second one. I think it'd be nice to mix up the speakers, so I'd like to leave maps and structs to someone else. Could do errors, depending on what @grrtrr chooses, or basics if nobody else wants it.
Do you think it would be a good idea to use pull requests for the slides and a two thumbs up review? (I assume we will continue editing them for consistency as we go too)

@nathany Would prefer errors if that is ok with you.

@nathany I haven't learned how to do pull requests yet, but that would be ok with me if the overhead is low.
I think a formal review process is more important for code, since a bug in code pushed to master can cause lots of problems for others, but errors in one person's slides won't mess up anyone else. We should still have a review process because we want high-quality presentations, but I'm not concerned if slides are pushed to master before they're polished.
So either way is fine with me.

@stellentus To do a pull request, you just push a branch to this repository, and the GitHub UI will present the option to open a pull request. See the help for more.

Let's decide on who's doing the rest of these talks so we can get the slides ready. Only 3 weeks left!

@matthias-stone I filled in the 'Error' slot. Am available after 1pm, can fill in one more slot if need to.

I added myself for maps in google doc.

@grrtrr some error handling resources: https://blog.golang.org/error-handling-and-go https://github.com/RobotsAndPencils/buford/blob/master/pushpackage/pushpackage.go with usage at https://github.com/RobotsAndPencils/buford#website-push.

@matthias-stone Do you have an existing outline for control structures? (even if you're not doing that talk)

"since a bug in code pushed to master can cause lots of problems for others"

Since the code is in ordinary Go files, I can setup Travis CI or similar to at least build the code. Feel free to write tests even if they aren't part of the code being demonstrated.

I'm interested in doing Types and Structs.

@nathany Sorry, pushed the wrong branch. Updated control structures.

thanks. @matthias-stone @lukaszroz are you opening pull requests for your branches?

Has everyone had a chance to walk through their slides?
My basics talk was just under 10 and slices was 19! But I did have a lot of questions from the audience, especially on the later.

Functions: 12 minutes without questions
Methods: 7 minutes without questions

We gave the workshop 7 months ago. I believe that means the talks were divided.


Incorrect return code when invoked without arguments?

Full disclaimer, I'm a devops guy just trying to support a new project so I had zero experience with basis prior to this.
I was trying to validate that I had the tool correctly installed by simply invoking the basisu command but the output that I got was:
npm i -g basisu fs-extra
basisu
err: Error: Command failed: /usr/local/lib/node_modules/basisu/bin/linux/x64/basisu

You can replicate the error with:
docker run                                  \
  --platform=linux/amd64 -it --rm           \
  --env NPM_CONFIG_UPDATE_NOTIFIER=false    \
  node:16-bullseye-slim                     \
  npx --yes -p fs-extra -p basisu           \
  basisu

I finally tracked down that basisu is returning EXIT_FAILURE after printing the usage message.
https://github.com/BinomialLLC/basis_universal/blob/44e1bcd3e145d18eb29d2915581ad4c61bb65cc7/basisu_tool.cpp#L4384-L4388
This wouldn't ordinarily be an issue, plenty of other linux commands return EXIT_FAILURE when invoked without arguments, but...
When installed via npm, the wrapper invocation script basisu.js invokes the basisu runtime via child_process.execFile and that considers any non-zero return code to be a failure which ends up swallowing the output and leaves the user baffled.
https://github.com/HacksawStudios/basisu/blob/master/bin/basisu.js#L35-L40
It seems to me that printing usage should return a non-error code since the behavior is not an abnormal codepath but that is 100% subjective and there are plenty of examples either way.
Is it a reasonable request to change line 4387 to EXIT_SUCCESS?

It seems to me that printing usage should return a non-error code since the behavior is not an abnormal codepath but that is 100% subjective and there are plenty of examples either way.

I don't really know - it's a good point and I've wondered it myself. I'll change this - shouldn't be an issue.
Thanks!


Add Haskell Makers

Thanks a lot for doing this, Syntastic's synchronous checking is what made me switch to neovim...
I'm trying to get haskell checking working with ghc-mod and hlint. Adapting the Synastic checkers mostly works, but some error messages are missing or end up looking funky.
Here's a sample file:
module Main where

main = return ()

-- | no type binding
toplevel n = n

-- | eta reduce
etared s l = map s l

-- | why not concat map
cm t r = concat $ map t r

The makers:
let g:neomake_haskell_ghcmod_maker = {
    \ 'exe': 'ghc-mod',
    \ 'args': ['check'],
    \ 'errorformat':
        \ '%-G%\s%#,' .
        \ '%f:%l:%c:%trror: %m,' .
        \ '%f:%l:%c:%tarning: %m,'.
        \ '%f:%l:%c: %trror: %m,' .
        \ '%f:%l:%c: %tarning: %m,' .
        \ '%f:%l:%c:%m,' .
        \ '%E%f:%l:%c:,' .
        \ '%Z%m'
    \ }
let g:neomake_haskell_hlint_maker = {
    \ 'errorformat':
        \ '%E%f:%l:%v: Error: %m,' .
        \ '%W%f:%l:%v: Warning: %m,' .
        \ '%C%m'
    \ }
let g:neomake_haskell_enabled_makers = ['ghcmod', 'hlint']

The checker's output:
$ ghc-mod check test.hs                                                                                [14:44:29]
test.hs:3:1:Warning: Top-level binding with no type signature: main :: IO ()
test.hs:6:1:Warning: Top-level binding with no type signature:  toplevel :: forall t. t -> t
test.hs:9:1:Warning: Top-level binding with no type signature:  etared :: forall a b. (a -> b) -> [a] -> [b]
test.hs:12:1:Warning: Top-level binding with no type signature:  cm :: forall a a1. (a1 -> [a]) -> [a1] -> [a]

$ hlint test.hs                                                                                [14:44:32]
test.hs:9:1: Error: Eta reduce
Found:
  etared s l = map s l
Why not:
  etared = map

test.hs:12:10: Error: Use concatMap
Found:
  concat $ map t r
Why not:
  concatMap t r

2 suggestions

and finally the location list after running Neomake:
test.hs|9 col 1 error| Eta reduce Found: etared s l = map s l Why not: etared = map
||
test.hs|12 col 10 error| Use concatMap Found: concat $ map t r Why not: concatMap t r
||
|| 2 suggestions
test.hs|3 col 1 warning| Top-level binding with no type signature: main :: IO ()
test.hs|6 col 1 warning| Top-level binding with no type signature:
test.hs|9 col 1 warning| Top-level binding with no type signature:
test.hs|12 col 1 warning| Top-level binding with no type signature:

You can see extra lines , and the "2 suggestions" from HLint's output, while everything after ghc-mod's first suggestion is dropped.
A solution or pointers on how to proceed would be great.

Wrt the extra lines, see #27. About the parts of the message that are missing, I'm guessing the errorformat is somehow wrong. When I have ported makers from syntastic and it doesn't work right, usually there is some subtle difference between the errorformats.  I can't look at it right away, but if you don't have any luck with it I'd be happy to try my hand at it sometime soon.

I actually think this has to do with #15. When I ran each linter in isolation, it worked perfectly. Do you get the same results every time? It's possible that some multiline messages are getting split up between two different job activity handler calls. Try putting let g:neomake_serialize = 1 somewhere in your ~/.vimrc and let me know if that fixes it.

Hmm, when I enable neomake_serialize I don't receive any hints from ghcmod at all(although I do get Neomake: ghcmod complete).
When I change haskell_enabled_makers to only ghcmod, I get the same erroneous output as above(without the HLint feeback).

Ok, I would make sure your version of neovim is relatively recent. I've been building weekly from master and testing agains that. Sometime this weekend I'll see if I can't get this going for myself and track down the different issues here.

Still happening off of nightly.
It seems specific to the top-level binding warning, I don't see it happening with others during my normal use.
Let me know if you need help getting set up. Usually you can just install cabal-install via your package manager, then run:
cabal update && cabal install hlint ghc-mod && export PATH=~/.cabal/bin/:$PATH.

It looks like I was able to figure this out. When running this linters in normal vim, I saw it was outputting ^A at each place that was breaking in neovim. So I did some digging with ghc-mod check test.hs | hexdump and saw that ghc-mod is outputting a null byte at each location that breaks. Neovim breaks in a different way from vim; it interprets null bytes in stdout from jobs as newlines it seems. This has come up as a problem with ghc-mod before.
I was able to fix it with a small output formatting step. I included both these makers in the repo as well.

Beautiful, thanks :)


Rationalise all form and button elements

Rationalise all form and button elements and create rules for them:

buttons (primary, secondary, tertiary)
default, hover and focus states

5 March 2020:

carry on with looking at toggle for viewer, explore with labels e.g. icon only, expanded with label

16 March 2020: collecting viewer improvement suggestions and putting into a presentable format - GO/DMa

26 March 2020

GO to package for zeplin and link to on this ticket
GO/devs to get the form elements added to Cardigan

Sketch artboards on Zeplin here:
zpl://project?tags=Form%20%26%20Buttons%20elements&pid=5aab926b4b6efde01259e959
https://zpl.io/V1nxDAQ

Something for discussion with @GarethOrmerod and @DominiqueMarshall
I'm not sure what to do about focus states on links when they've been clicked rather than tabbed-to with the keyboard. Would you expect e.g. the main navigation links to receive the turquoise border styles from the recent design updates when they were clicked?

We currently use a css reset that hides any focus style when you're hovering a link, but I'm experiencing some existential doubt about whether or not this is appropriate (and if not, it would re-open the debate about whether or not a button should retain its focused style after it has been clicked).
FWIW I see that e.g. gov.uk and southbankcentre.co.uk (who have implemented the kind of bold custom focus styles we're looking to go with) apply the focus style regardless of whether it's clicked on or keyboard-ed.

Following up on discussing this with the team, the most appropriate direction would be for the focus state to be visible when tabbing using a keyboard but not always necessary when using mouse/trackpad.
The design system should highlight an active state if it is needed without relying on :focus. e.g. tabbed navigation or accordions.
The instance where it is needed is within a form where highlighting the currently active form is beneficial.

@davidpmccormick do we know why an item is focussed when clicked? It feels like a deliberate choice by the browser devs and thus might have a use case?

I can imagine if you were to arrive on a page and focus was directed to a particular element, at that point the browser wouldn't have any knowledge of whether you were a mouse or keyboard user, so ensuring focus was visible to keyboard users would be the priority. If we default to this for server-rendered pages (by the addition of an initially-present is-keyboard class), then I think we're being good a11y citizens.

Closing as remaining button work is covered by #5230.


feat: Added AWS Cloudwatch Metrics receiver

Proposed Change
Added the aws cloudwatch metrics receiver
Checklist

[ ] Changes are tested
[ ] CI has passed

Receiver doesn't seem to be implemented?

Good catch @BinaryFissionGames I'll close this PR.


Zugferd importer does not recognize XRechnung Zugferd Profile

A PDF with an embedded XRechnung like this
<ram:GuidelineSpecifiedDocumentContextParameter>
    <ram:ID>urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0</ram:ID>
</ram:GuidelineSpecifiedDocumentContextParameter>

is recognized as a valid Zugferd Document, but no Profile could be found for it.
Would it make sense to change the getZugferdProfile() method in the ZUGFeRDImporter.java
    public String getZUGFeRDProfil() {
        switch (this.extractString("//*[local-name() = 'GuidelineSpecifiedDocumentContextParameter']//*[local-name() = 'ID']")) {
            case "urn:cen.eu:en16931:2017":
            case "urn:ferd:CrossIndustryDocument:invoice:1p0:comfort":
                return "COMFORT";
            case "urn:cen.eu:en16931:2017#compliant#urn:factur-x.eu:1p0:basic":
            case "urn:ferd:CrossIndustryDocument:invoice:1p0:basic":
                return "BASIC";
            case "urn:factur-x.eu:1p0:basicwl":
                return "BASIC WL";
            case "urn:factur-x.eu:1p0:minimum":
                return "MINIMUM";
            case "urn:ferd:CrossIndustryDocument:invoice:1p0:extended":
            case "urn:cen.eu:en16931:2017#conformant#urn:factur-x.eu:1p0:extended":
                return "EXTENDED";
            // new addition
            case "urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0":
                return "XRECHNUNG";
            default:
                return "";
        }
    }

Or would it be better to fold this into EXTENDED?

sounds like a very good idea👍, actually it would be sufficient to scan for "xrechnung" in the guideline ID to return XRechnung, no need to restrict to version 3...

That would mean breaking up the switch, probably, but that's fine. I'll try to send in a PR later today.


Don't merge dev dependencies  with "app" dependencies

Keep package.json clear

Yes, I myself noticed that in this template that I used very poorly distributed packages. I will fix it very soon. Thanks for following our code!


AntiForgeryToken is broken - Server cannot append header after HTTP headers have been sent.

I am implementing AntiForgeryToken my login form.
When I run project, its call Account/Login Get mothod and return view() i.e login.cshtml
In login.cshtml view page, I have
@using (Html.BeginForm("Login", "Account", new { ReturnUrl = ViewBag.ReturnUrl }, FormMethod.Post, new { @class = "form1" }))
{
    @Html.AntiForgeryToken(); // throw exception

    @Html.TextBoxFor(m => m.UserName, new { placeholder = "UserName", autofocus = true })

    @Html.TextBoxFor(m => m.Password, new { type = "password", placeholder = "Password" })

@Html.ValidationSummary(false, "", new { @class = "msg error" })

    <input type="submit" name="login" value="Login" id="btnLogin" />

Forgot Password?

}

When server return login.cshtml page I got this exception
I am implementing AntiForgeryToken my login form.
When I run project, its call Account/Login Get mothod and return view() i.e login.cshtml
In login.cshtml view page, I have
@using (Html.BeginForm("Login", "Account", new { ReturnUrl = ViewBag.ReturnUrl }, FormMethod.Post, new { @class = "form1" }))
{
    @Html.AntiForgeryToken(); // throw exception

    @Html.TextBoxFor(m => m.UserName, new { placeholder = "UserName", autofocus = true })

    @Html.TextBoxFor(m => m.Password, new { type = "password", placeholder = "Password" })

@Html.ValidationSummary(false, "", new { @class = "msg error" })

    <input type="submit" name="login" value="Login" id="btnLogin" />

Forgot Password?

}

When server return login.cshtml page
Server cannot append header after HTTP headers have been sent.
I can not figure out how to solve this error.
Thank you,

This message means that something is happening that's causing the server to start sending data back to the client before you add the cookie for antiforgery. Do you have a Flush() in your layout page?
If you have a small isolated repro of this you put in a repository we have access to we can help you troubleshoot the problem.

Closing until we have a repro. This is almost certainly what @rynowak stated. If you can share a repro project we can take another look at this.

Sorry for late reply, I created new project and I am not able to regenerate an issue, may be @rynowak  is right that something is happening that's causing the server to start seding data back to the client. So I created new new project and transfer all login and code to new created project and from now I am not getting such error. And also cliam Antiforgery Token in global.
AntiForgeryConfig.UniqueClaimTypeIdentifier = ClaimTypes.NameIdentifier;


Add back test target to circleci nightly

We previously added back some targets to run on circleci nightly so we
can compare to prow, but the test target was deleted so the tests are
failing. This just adds the same test target back.
Fixes https://github.com/istio/istio/issues/15374
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[x] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: howardjohn
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

.circleci/OWNERS [howardjohn]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@howardjohn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-istioctl-k8s-presubmit-tests.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test integ-istioctl-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-istioctl-k8s-presubmit-tests.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test integ-istioctl-k8s-presubmit-tests-master

prow/codecov.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test istio-codecov-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-istioctl-k8s-presubmit-tests.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test integ-istioctl-k8s-presubmit-tests-master

prow/codecov.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test istio-codecov-master

prow/integ-new-installer-k8s-presubmit-tests.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test integ-new-install-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-istioctl-k8s-presubmit-tests.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test integ-istioctl-k8s-presubmit-tests-master

prow/codecov.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test istio-codecov-master

prow/integ-new-installer-k8s-presubmit-tests.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test integ-new-install-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test integ-mixer-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/codecov.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test istio-codecov-master

prow/integ-mixer-k8s-presubmit-tests.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test integ-mixer-k8s-presubmit-tests-master

prow/integ-new-installer-k8s-presubmit-tests.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test integ-new-install-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test all

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/codecov.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test istio-codecov-master

prow/integ-mixer-k8s-presubmit-tests.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test integ-mixer-k8s-presubmit-tests-master

prow/integ-new-installer-k8s-presubmit-tests.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test integ-new-install-k8s-presubmit-tests-master

prow/integ-telemetry-k8s-presubmit-tests.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test integ-telemetry-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-mixer-k8s-presubmit-tests.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test integ-mixer-k8s-presubmit-tests-master

prow/integ-telemetry-k8s-presubmit-tests.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test integ-telemetry-k8s-presubmit-tests-master

prow/integ-new-installer-k8s-presubmit-tests.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test integ-new-install-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-mixer-k8s-presubmit-tests.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test integ-mixer-k8s-presubmit-tests-master

prow/integ-telemetry-k8s-presubmit-tests.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test integ-telemetry-k8s-presubmit-tests-master

prow/integ-new-installer-k8s-presubmit-tests.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test integ-new-install-k8s-presubmit-tests-master

prow/e2e_pilotv2_auth_sds.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test istio_auth_sds_e2e-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-telemetry-k8s-presubmit-tests.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test integ-telemetry-k8s-presubmit-tests-master

prow/integ-new-installer-k8s-presubmit-tests.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test integ-new-install-k8s-presubmit-tests-master

prow/e2e_pilotv2_auth_sds.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test istio_auth_sds_e2e-master

prow/integ-mixer-k8s-presubmit-tests.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test integ-mixer-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/assign @costinm

/test istio_auth_sds_e2e-master

/assign @utka

/lgtm

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-telemetry-k8s-presubmit-tests.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test integ-telemetry-k8s-presubmit-tests-master

prow/integ-new-installer-k8s-presubmit-tests.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test integ-new-install-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test integ-mixer-k8s-presubmit-tests-master

prow/codecov.sh
9538939f36c70f1e96cf40aeb0e3865b8777d8fe
link
/test istio-codecov-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-codecov-master


Incorrect v3 TypeScript types for ChartDataset

Expected Behavior
This is working and correct ChartDataset configuration (in v3) that should work (and works fine after muting TS errors):
const dataset: ChartDataset = {
  data: [5, null, 7],
  fill: true,
};

Current Behavior
data is expected to be a number[]. But null values are perfectly fine (and needed), so the type should be (number | null)[]. Moreover, after changing dataset type to ChartDataset<'line'>, the expected type is ScatterDataPoint[] and even an array of numbers is not accepted.
fill is expected to be string | number | false | _DeepPartialObject<{ value: number; }> | _DeepPartialObject<ComplexFillTarget> | undefined, and it does not accept true 🙂
Environment

Chart.js version: 3.0.0-rc.2

Btw, great to see built-in types in the library!

Thanks for reporting this.
For the fill to support true, it's a quick change. For the data, I believe this can be supported. Only line, scatter, and radar charts support null so it's a small change.

This was like the fastest issue resolution ever in open-source history!


Bug: Pipeline Status Stuck on "Deleting" After Deletion the pipeline

📜 Description
encountering an issue where after deleting a pipeline, the UI continues to show the pipeline status as "Deleting"
Affected areas
Other CRITICAL functionality
Additional affected areas
Other CRITICAL functionality
Prod/Non-prod environments?
Prod
Is User unblocked?
None
How was the user un-blocked?
None
Impact on Enterprise
the pipeline status remains as "Deleting" even after deleting the pipeline
👟 Steps to replicate the Issue
NA
👍 Expected behavior
The pipeline should be removed from the UI, or if deletion is still in progress, the status should accurately reflect that.
👎 Actual Behavior
The pipeline status remains as "Deleting" even after deleting the pipeline
☸ Kubernetes version
1.30
Cloud provider

GCP

🌍 Browser
Chrome
✅ Proposed Solution
No response
👀 Have you spent some time to check if this issue has been raised before?

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

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Duplicate of https://github.com/devtron-labs/devtron/issues/5774


Remove unneeded id from breadcrumbs

What is the context of this PR?
Fixes: #1231
This is a BREAKING CHANGE for Breadcrumbs in Runner because ids will no longer be able to be used in tests
How to review
Check breadcrumbs still work as expected

 Issue #1231: Empty ID’s break W3C validation

You could put an if around the id to prevent this being breaking or you would need to provide a data- (inside an if) so runner can still test the link.

You could put an if around the id to prevent this being breaking or you would need to provide a data- (inside an if) so runner can still test the link.

Yeah that could be a good idea, I was just thinking as you said that they should really be using data attributes and this would mean they would have to use them. But thinking about it now, maybe a non breaking change would be good. So ill put the if round it


Bump transformers and accelerate versions

Description

The incoming Chronos version depends on accelerate version 0.32 and runs stable with version 0.34, which is the last version of accelerate before its v1.0 release. In AG, accelerate is capped at v0.22.
Transformers dependency is also now 5 minor versions behind. Chronos runs stable with v4.39. The latest version is v4.46. AG cap is at 4.41.

This is a tracking issue to bump these dependencies to
"transformers[sentencepiece]": ">=4.39.0,<4.47",
"accelerate": ">=0.32,<1",

References

updated at PR


Adds support for gulp.watch

This adds file watching support by way of gulp.watch to our gulp build.

ping @weswigham


[Feat] Enable PluginManager::nn_preload

In this PR, the PluginManager::nn_preload API in wasmedge-sdk is enabled. In addition, improve the original argument design.

Hello, I am a code review bot on flows.network.
It could take a few minutes for me to analyze this PR. Relax, grab a cup of coffee and check back later. Thanks!

@hydai Could you please help review this PR? Thanks a lot!

@hydai Thanks for the review!