intermittent issue - video.offset is not a function

Hello,
Using the latest release, and I get an intermittent error where the offset plugin will not work.
<script src="http://vjs.zencdn.net/5.18.4/video.js"></script>
<script src="http://<IP_ADDRESS>/video-js/offset/videojs-offset.1.0.1.js">

video = videojs('example_video_1');
video.offset({start: 100, end: 200, restart_beginning: true });

Uncaught TypeError: video.offset is not a function
This happens roughly 5% of the time.  A page reload usually fixes it.  I've been stuck on this for a few days, any help would be greatly appreciated.
J

Hi @elevenpast ,
In order to use offset plugin you must initialise the plugin as follows:
videojs('my-video', {
  plugins: {
    offset: {
      start: 10, //Start offset in seconds
      end: 40,    //End offset in seconds
      restart_beginning: false //Should the video go to the beginning when it ends
    }
  }
});

Otherwise videojs won't import the plugin and expose its methods.

Hello,
I've tried both methods and both give me intermittent failures.
The Videojs docs on Github show that either method can be used (https://github.com/videojs/video.js/blob/master/docs/guides/plugins.md).

Setting up a Plugin
There are two ways to set up (or initialize) a plugin on a player. Both ways work identically for both basic and advanced plugins.
The first way is during creation of the player. Using the plugins option, a plugin can be automatically set up on a player:
videojs('example-player', {
plugins: {
examplePlugin: {
customClass: 'example-class'
}
}
});
Otherwise, a plugin can be manually set up:
var player = videojs('example-player');
player.examplePlugin({customClass: 'example-class'});
These two methods are functionally identical - use whichever you prefer!

I can change it back to the other method as you suggest, but the problem will still be there.
J

Confirmed, but the error message is different.  Plugin not found: offset
Again, it works fine most of the time, but I get an error about 1 out of 20.
J

Such intermittent errors point to a rather assets-loading problem. Perhaps, sometimes your code is attempting to initialise videojs before the scripts are fully loaded in your page?
Are you loading you javscripts files using something like SystemJs that might be loading your them asynchronously?
Try to load you page with "No Cache" options enabled in your dev tools. I bet the error will now occur 100% of the times.

I'm not using SystemJs or anything like that.
I am testing on a machine with much slower internet, and it occurs 50% of the time.  So it seems like a race condition for sure.   How I can avoid that?
J

Make sure you load all vendors' scripts including offset plugin before load and run your app code.
Then, surround your code in a function so you are sure your code is evaluated when your page is ready.
This is your example code:
<script src="http://vjs.zencdn.net/5.18.4/video.js"></script>
<script src="http://<IP_ADDRESS>/video-js/offset/videojs-offset.1.0.1.js">

video = videojs('example_video_1');
video.offset({start: 100, end: 200, restart_beginning: true });

Try replacing it by
<script src="http://vjs.zencdn.net/5.18.4/video.js"></script>
<script src="http://<IP_ADDRESS>/video-js/offset/videojs-offset.1.0.1.js">

(function() {
  video = videojs('example_video_1');
  video.offset({start: 100, end: 200, restart_beginning: true });
)();

Sorry if you already tried this :P

Haven't tried that, I'm unfamiliar with that approach.   Something isn't right with the syntax though.
J

Check this out:
http://plnkr.co/edit/iD4stUXyDS7ipTtnHltL?p=preview

I think you cracked it!!!!
The function() seems to do the trick, thanks so much for your help and getting me out of a jam.
Josh

Glad we sort it out.
I'm closing the issue.
Cheers!


Display the Body on exception_with_response

Sometimes REST servers respond with error messages in the body, but the RestClient::AbstractResponse method exception_with_response only returns the code and not the body.
I'd like to request the feature to return the body if it's not empty somewhere in here:
https://github.com/rest-client/rest-client/blob/master/lib/restclient/abstract_response.rb#L242-L250
That way I don't have to PRY into your gem just to return the body to see why my request failed.

@pescetto
exception_with_response raises the exception with the response code and its message. If you want to get the response/error_messages try this:
begin      RestClient.get 'http://example.com/nonexistent'    rescue RestClient::ExceptionWithResponse => e      e.response.body    end

As already noted, the ExceptionWithResponse objects contain a #response method that allows you to get the entire response object along with its body and any other fields.

We use bug tracking software that reports the class name and message (as well as the stacktrace). By duplicating the class name in the message and adding bespoke properties means that this error handling technique needs custom code outside of the standard exception paradigm.
Is there a reason that the error response can't be the message in the exception when the message is blank? Seems like an easy win without a good reason otherwise.
Currently we have:
rescue RestClient::Exception => re
    ExceptionHelper.track_exception(re)

But what we needed to do to get anything useful is:
rescue RestClient::Exception => re
    re.message = re.http_body if re.http_body
    ExceptionHelper.track_exception(re)

And repeat everywhere we catch a RestClient::Exception
This could be done easily within exceptions.rb by changing
def message
  @message || default_message
end

to
def message
  @message || response.body || default_message
end

or similar (might be better in default_message as a more verbose fallback).


Add a bedspace to a property

Changes in this PR

A user can add a bedspace

Screenshots of UI changes

 Add a bedspace to a property


[FEATURE] Role reshaping

Description
Lately we've been making some changes to our roles and this role lags behind the rest of the roles in some aspects:

There is no .gitattributes file: https://github.com/idealista/jira_role/blob/master/.gitattributes
There is no travis email notification config: https://github.com/idealista/jira_role/blob/master/.travis.yml#L20-L25
Some versions in the Pipfile could be updated, at least the patch version (be aware to not break CI): https://github.com/idealista/jira_role/blob/master/Pipfile
Add ansible-lint as dependency in the Pipfile and its config: https://github.com/idealista/jira_role/blob/master/.ansible-lint. Include ansible-lint in molecule linting stage: https://github.com/idealista/jira_role/blob/master/molecule/default/molecule.yml#L8
Some warnings may arise because of the introduction of ansible-lint. It could be positive to fix them.

Why is this needed?
So the role is updated along all the roles
Additional Information
N/A

Also .github directory and its corresponding files should be added:  https://github.com/idealista/cookiecutter-ansible-role/tree/develop/{{cookiecutter.app_name}}_role/.github


Unbonding

I am trying to unbond my tokens and it has been over a week, on the main page it says I can unbond in approximatly 5 years? what gives, it is supposed to be 7 days

Hey @tnels79 - please make sure you using the new explorer. The classic explorer is no longer maintained and is bug prone.

Thank you  Adam, that worked
On Sun, Aug 9, 2020, 4:13 PM Adam Soffer<EMAIL_ADDRESS>wrote:

Hey @tnels79 https://github.com/tnels79 - please make sure you're using
the new explorer https://explorer.livepeer.org. The classic explorer is
no longer maintained and is bug prone.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/livepeer/livepeerjs/issues/811#issuecomment-671101736,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APFMUJ7VMQAXPQPVSXRZ5C3R74GO7ANCNFSM4PZLZMVQ
.


Press Enter to Send

I would like to recommend you to add a toggle feature already existing on the official Facebook website:
"Press Enter to Send." which would allow users to write paragraphs rather than just a single block of text and avoid sending a message by mistake.

If you want to go to the next line, you can use shift+enter.

@rajatshah92  Exactly. Both Ctrl+Enter or Shift+Enter would go to the next line. In fact, most messenger or send-upon-enter text box works like this.


Set-CsLisCivicAddress details in the document and background

[Enter feedback here]
The part not mentioned on the document is that the fact I observed which the certificate(.pfx) will be stored in the Personal Certificate Store instead of Local Machine in the process, which is related to the step when it comes to the PScmdlet Test-CsCivicAddress.
In the case for a large org which happens to have multiple admins for their SfB and the admin who didn't originally configure the  LIS provider with the Set-CsLisServiceProvider on the machine, the specific admin wouldn't be able to leverage the certificate for him/her personal certificate store and could end up with the error "Could not create SSL/TLS secure channel"
Just a though it would be something we want to provide the background in the document.
Thanks.

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

ID: e505d937-c075-bab3-0103-ac5f93df9372
Version Independent ID: 98b66f30-07a8-37b9-e82d-6cda847cd25c
Content: Set-CsLisServiceProvider (SkypeForBusiness)
Content Source: skype/skype-ps/skype/Set-CsLisServiceProvider.md
Service: skypeforbusiness-powershell
GitHub Login: @hirenshah1
Microsoft Alias: hirshah

Correction: I meant to refer the PScmdlet Test-CsLisCivicAddress instead of Test-CsCivicAddress in the report

Duplicate of https://github.com/MicrosoftDocs/office-docs-powershell/issues/9797


feat(storage): add sanity check for storage table in debug mode

Signed-off-by: Alex Chi<EMAIL_ADDRESS>I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
So that we can detect error earlier!
Checklist

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

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

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

Release note
Please create a release note for your changes. In the release note, focus on the impact on users, and mention the environment or conditions where the impact may occur.
Refer to a related PR or issue link (optional)
ref https://github.com/singularity-data/risingwave/issues/3887
ref https://github.com/singularity-data/risingwave/issues/3885
ref https://github.com/singularity-data/risingwave/issues/3893

TPC-H Q22 failed
thread 'tokio-runtime-worker' panicked at 'overwriting an existing row:
in-storage: Row([Some(Decimal(Normalized(4610.9775)))])
to-be-written: Row([Some(Decimal(Normalized(4875.0083333333333333333333333)))])', /risingwave/src/storage/src/table/storage_table.rs:422:25
stack backtrace:
   0: rust_begin_unwind

Shall we disable it for now, and get this sanity check merged first? I guess this is the reason why it caused e2e randomly fail. cc @fuyufjh @jon-chuang

Disabled sanity check for dynamic filter.


Auto-update zmqpb to 0.6

New version of zmqpb detected (package version: nil, last github version: 0.6)

done in #3712


humioctl: init at 0.25.0

Motivation for this change
This PR adds the CLI for Humio, humioctl, to nixpkgs.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@kalbasit Any chance I can get a +1 on this? :)

/marvin opt-in
/status awaiting_changes

@GrahamcOfBorg build humioctl


As a database administrator, I want to generate a report of the capital cities in a region organised by largest to smallest to estimate equipment cost.

Editing title to match report #19
All the capital cities in a region organised by largest to smallest


project status?

Hello, I am very interested in this project and I would like to be able to contribute to this repo, since there are many libraries for the arduino IDE, and now the development with micropython, and especially with the arq ARM, is taking a lot of strength.
I say this since I have tried to rebuild some functional modules of Arduino and now I can pass them to the Micropython project.
Thank you

Hi,
Thank you for your attention to this project. You can build your Ardupy firmware through aip. With aip, you can bind the converted Arduino library to microython. This is an example seeed-ardupy-ultrasonic-sensor


The presence of N+1 queries while using Turbo causes response times to consistently increase

The problem is that response times consistently and gradually increase when there is an N+1 query and prosopite is enabled and Turbo is being used. The simplest way to reproduce the issue seems to be paginating over a large set of data that includes a count of related records.
I created this repository to help easily see the issue - the readme outlines how to set it up and reproduce it:
https://github.com/JamesChevalier/turbo_response_slowdown
I tried to make the commits in a way that also helped give a view of only the relevant parts. This commit is the most relevant view of the issue.
Versions of relevant pieces:

Ruby 3.0.2
Rails <IP_ADDRESS>
prosopite 1.0.3
turbo-rails 7.1.0
@hotwired/turbo 7.0.1

I suppose the fix is to not have N+1 queries. 😅 😆

Do you mean this happens in development? As per the README, the it should not be enabled on production:
  unless Rails.env.production?
    around_action :n_plus_one_detection

    def n_plus_one_detection
      Prosopite.scan
      yield
    ensure
      Prosopite.finish
    end
  end

Do you mean this happens in development?

Yes. I believe my reproduction repository is also set up to demonstrate that.


Error when response content type is application/pdf

Context
I am trying to document a PDF content type response in an openapi spec, and mock the response by running prism mock path/to/file.
Current Behavior
When I attempt the process described above,  I get the error: Request terminated with error: Error: Cannot find serializer for application/pdf.
An example of the spec (that follows the latest syntax and best practice) that causes the problem:
responses:
  200:
    description: OK
    content:
      application/pdf:
        schema:
          type: string
          format: binary
        examples:
          default:
            summary: A sample report
            externalValue: "https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf"

Expected Behavior
I've never seen it working, so I can't really describe what I expect to happen, other than I expect it to work without an error, and I expect to be able to download the PDF file sent in the response when testing the mock server in a tool such as Stoplight or Redocly.
Possible Workaround/Solution
Just providing the URL of the example PDF document as a string instead of using the externalValue property removes the error from the Prism CLI output, however when attempting to actually download the file, it is corrupted or fails to open. But it's arguabaly a better experience than an outright error, albeit still not a solution.
responses:
  200:
    description: OK
    content:
      application/pdf:
        schema:
          type: string
          format: binary
        examples:
          - "https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf"

Hi ! Is there some news on supporting local or external PDF files ?


not able to read "$EXTMIN" and "$EXTMAX" values from DXF files.

Hi,
Now I have some dxf files which are generated by Tekla Structure Software version 2021.
For these dxf files, I am not able to read their "$EXTMIN" and "$EXTMAX" values since values are not in the proper format.
example :-
$EXTMIN
10
1.000000000000000E+20
20
1.000000000000000E+20
30
1.000000000000000E+20
9
$EXTMAX
10
-1.000000000000000E+20
20
-1.000000000000000E+20
30
-1.000000000000000E+20
9
But when I opened this file in AutoCAD and saved it after that I am able to read its $EXTMIN and $EXTMAX values.
So could you please provide me with a solution for the above issue?
Is it possible to open the dxf file and save it and again use this file for another task without losing its data?
Thanks.

First thanks for the response.
My problem is when my tool trying to read dxf file which is exported from Tekla Structure that time its EXTMIN and EXTMAX values are not in the proper format they are like "1.000000000000000E+20" this kind of number, but when I open the same dxf file in Autocad that time these 2 variables having proper decimal values and also readable through my tool.
Following are those 2 variables and their values.
$EXTMIN
10
3392.128751969677
20
4474.958629929921
30
0.0
9
$EXTMAX
10
4475.846394006834
20
4788.772733162242
30
0.0
9
so I am asking you for advice if you have any ideas or suggestions, instead of manually opening and saving those dxf files which are exported from Tekla Structure how can I automate this task using netDXF or any other way.
thanks.

Why the scientific notation is causing you problems? Writing a million as 1000000 or 1e6 are both valid ways of expressing numbers, so whatever you are doing you should be able to handle them. All programming languages will manipulate them easily, at least the ones I know of.

Thanks for the response I have solved the issue now.


Unable to start visor node due to command line changes

2022/10/31 15:58:56 Initiating node "validator" with: /home/jake/go/bin/vega [init --home /workspace/networkdata/testnet/vega/node3 --nodewallet-passphrase-file /workspace/networkdata/testnet/vega/node3/node-vega-wallet-pass.txt --no-tendermint --output json validator]
Error: failed to generate network: failed to initiate Vega node id 0 for node set validators: failed to initiate vega node: failed to execute binary /home/jake/go/bin/vega [init --home /workspace/networkdata/testnet/vega/node0 --nodewallet-passphrase-file /workspace/networkdata/testnet/vega/node0/node-vega-wallet-pass.txt --no-tendermint --output json validator] with error: unknown flag `no-tendermint'
: exit status 255
make: *** [Makefile:270: start-network] Error 1

As of fb9b116691f16cca81df75f51a7c0cca0561aef2 (vegacapsule) and some time before 1c76ad7b8678dfeeb9239b801ecc888f1e7b0c76 (vega), I am unable to start a network with visor nodes (which is what https://github.com/vegaprotocol/system-tests/pull/1322 branch uses for the network_infra test run).

Turns out that this was caused by:
https://github.com/vegaprotocol/vegacapsule/issues/305
(i.e: my local environment picked up an old vega binary because a recent change switched the system test network config to pick up vega from the path rather than the previously explicitly-specified network directory)


Create v5 data spec

Here are the data-specs that define the table names, columns, and any required coercions; the card mentions excluding coercions, but street segments already had a table that doesn't allow text values in some columns
Pivotal card
This is the second of three 5.0 CSV PRs, and blocks a PR about loading 5.0 CSVs

LGTM - it was actually a lot easier to look at all of these together, fwiw


Support for Stax + EVM

Add support for Stax device
Update SDK
Update Zemu test: include Stax and run tests in parallel
Added support for EVM path

Jira ticket : https://ledgerhq.atlassian.net/browse/B2CA-1305


Add ability to set reports directory via environment variable

This pull request add the ability to specify the reports directory via an environment variable. This is especially useful when setting the given reporter via the environment variable MINITEST_REPORTER.
Further, we're currently using Bitbucket Pipeline for CI purposes. They enforce certain expectations on where the Xunit-compatible output is located. Currently, we check for the CI environment variable in our test_helper.rb and change the reporter and the expected reports directory as needed. With this change, we could just set MINITEST_REPORTER and MINITEST_REPORTERS_REPORTS_DIR in our Bitbucket environment and remove any custom changes made explicitly for Bitbucket from our test_helper.rb.

Thank you for the contribution.  Sorry for late response.  Hope to publish a new version in a week.


Get-DbaInstanceProperty - Timeout waiting for temporary runspaces reached!

I look through a for each server list and run Get-DbaInstanceProperty, before putting results into DB table.
I start a job on each server in attempt to multi thread and make quicker, I then collect each job.
This has been working and previously I had no issues with this, but seems to have stopped working? I now have no InstanceProperty output into my table and PS Seems to spit out the following warning over and over:
"Timeout waiting for temporary runspaces reached! The Module import will complete, but some things may not work as intended
WARNING: [14:30:16][Get-DbaInstanceProperty] Failure | Unable to find type [Microsoft.SqlServer.Management.Smo.Server].
WARNING: The module import has hit a timeout while waiting for some background tasks to finish.
This may result in some commands not working as intended.
This should not happen under reasonable circumstances, please file an issue at:
https://github.com/sqlcollaborative/dbatools/issues
Or contact us directly in the #dbatools channel of the SQL Server Community Slack Channel:
https://dbatools.io/slack/"

Can you advise in this scenario?

Thanks much, can you run this again with the latest version? it should be fixed.


update go-rpio to v4.6.0 to support raspi4b.

fix issue: https://github.com/kubeedge/examples/issues/114
and update vendor file.

/assign

/close


Remove rostrum.blog.json

Alas, I converted to Quarto. Thank you for hosting rostrum.blog on awesome-blogdown all this time.

Apologies for the delay, Matt! Thanks for being a part of awesome blogdown and for the PR.


Various redis cache cleanup

Mostly variable renames but I also fixed a panic on misconfiguration.

I removed the functionality changes, its now 100% just renaming things.


[WIP] Add handling of compound nouns in JapaneseExpressionVariation

Coverage increased (+0.03%) to 91.137% when pulling 64ca201ccd7fcfc3fbcc45f2d8c934bed01e56e7 on takahi-i:concatinate-nouns into ef24ec053d4ca3bab8a307f773d5b3ce044fed81 on redpen-cc:master.


Scrollbar in the project selection section

This task is automatically imported from the old Task Issue Board and it was originally created by Greg Ociepka.
Original issue is here.

in both Open project dialogue window and homescreen
https://discord.com/channels/401396655599124480/1063051397655973938
Tasks:

[ ] Scrollbar for Home screen
[ ] Scrollbar for Open project dialog

Fixed in open project dialogue #5607 , and the homescreen will have a new version.


GH-40069: [C++] Use relaxed atomic store to write scalar scratch space

Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

GitHub Issue: #40069

Hi @bkietz , I had some bad news about the current approach.
The current approach did prevent WW race by using atomic stores. The reading, however, is using plane memory load, thus leads to RW race (observable by TSAN, at this line https://github.com/apache/arrow/pull/40237/files#diff-5af65f049e302f76671ecbfc17b0f9c522ec94be291b2bcb442fa565d3607736R2006). Given that the reading is through ArraySpan and spread all over the compute component, it is not feasible to change every read to atomic load.
So I have to turn to an alternative approach drafted in #40260, using DCLP which could prevent both WW and RW race conditions. Would you step to #40260 to take a look? (It's of course in draft and lacks tests of many other scalar types, but it would be nice to make agreement on the approach first)
Once we have an agreement on the new approach, I'll close this PR and move on with the other.
cc @pitrou

Ok, before we introduce even more complexity and ad-hoc synchronization, let's step back a bit and ask ourselves the question: why is a ArraySpan or BufferSpan being initialized concurrently? We should probably fix that, instead of adding bandaids so that it doesn't trigger TSAN warnings.

why is a ArraySpan or BufferSpan being initialized concurrently?

The problem is we want FillFromScalar to act like copying a constant value into the ArraySpan.  It would not be an error for multiple threads to copy a const int into a local int. However FillFromScalar mutates the constant scalar from which we're copying.
One way to resolve this without sync would be setting up the offset scratch space when the scalar is constructed. IIRC we didn't do that in the first place because there are places where we assign to BinaryScalar::value, which would invalidate the offsets. Cleaning those up would be annoying but is more in line with Scalar behaving as an immutable value

I think it would be good to move to an immutable-after-instantiation model. I don't think it's worth supporting the mutation of a Scalar after it was constructed.

OK, l can check how much work is needed to move to the immutable-after-instantiation approach.

Just a concern. Will this approach break the API compatibility? Since BaseBinaryScalar::value is already a public API and there might already have been user code that is assigning to it.

Sorry for coming back to this late. I'm pushing a new approach into this PR as previously discussed (thus the title change).
It is still WIP, with some further refactoring to be done and a little more tests to be added. But I think it is enough to show the essential of the approach. So I'd like to start the discussion now before further coding, to prevent any last minute surprise. There are two things:

The change in scalar.h may seem a little overkill, specifically the FillScalarScratchSpace and subclasses. This is because I want to mandate the initialization of the scratch space in the subclasses' constructors, meanwhile do it in a polymorphic fashion. Do you think this is proper?
So far I have only made the values immutable for subclasses of ArraySpanFillFromScalarScratchSpace. This is sufficient to ensure the validity of the scratch space content. But this doesn't fully achieve the goal of "making scalar absolutely immutable by all means" - which is doable (partially done in my other branch, not shown in this PR), but just requires a lot more changes. Should I move on towards the full-immutability?

I appreciate your feedback @pitrou @bkietz . Thanks.

The current approach, i.e., immutable value, has some corner cases uncovered with is_valid being mutable.
Say, a scalar instance is created with a valid value. Later setting its is_valid to false is fine because any attempt of using this scalar won't actually use the scratch space content. However it is not the case for the reverse: setting is_valid to true for an initially invalid scalar instance will leave the scratch space content inconsistent.
One way around it could be leveraging Scalar::Validate or Scalar::ValidateFull to detect such inconsistency, supposing user code should call these method aggressively to check the scalar.

Without early feedback, I just go ahead and now get the PR ready. The description has been updated accordingly. @pitrou @bkietz could you help to take a look? Thank you!

Thanks @bkietz for looking! I've rebased as you requested. Let's see the CI.

Hi @bkietz , shall we move on with this PR? Thanks.

The added test TestConcurrentFillFromScalar is failing on the emscripten build (https://github.com/ursacomputing/crossbow/actions/runs/8871520273/job/24354620994)
From a quick look at the diff here, I think it just needs some compile guards because the test requires threads to be available, like:
#ifndef ARROW_ENABLE_THREADING
  GTEST_SKIP() << "Test requires threading support";
#endif

The added test TestConcurrentFillFromScalar is failing on the emscripten build (ursacomputing/crossbow/actions/runs/8871520273/job/24354620994)
From a quick look at the diff here, I think it just needs some compile guards because the test requires threads to be available, like:
#ifndef ARROW_ENABLE_THREADING
  GTEST_SKIP() << "Test requires threading support";
#endif

Oops, didn't expect that coming. I'll file a quick fix. Thank you @jorisvandenbossche for locating the cause.
One question though (I'm not familiar with emscripten): is emscripten's threading compilable but not runnable?

One question though (I'm not familiar with emscripten): is emscripten's threading compilable but not runnable?

We have a compile flag to disable threading (ARROW_ENABLE_THREADING) which is disabled for the builds for emscripten (https://arrow.apache.org/docs/dev/developers/cpp/emscripten.html)


Eslint.

Codecov Report

Merging #84 into master will decrease coverage by 0.36%.
The diff coverage is 79.78%.

@@            Coverage Diff             @@
##           master      #84      +/-   ##
==========================================
- Coverage   92.15%   91.79%   -0.37%
==========================================
  Files          72       72
  Lines         931      938       +7
  Branches      205      208       +3
==========================================
+ Hits          858      861       +3
  Misses         34       34
- Partials       39       43       +4

Impacted Files
Coverage Δ

...rawmodel-handlers/src/handlers/mongo-uniqueness.ts
70.00% <ø> (ø)

packages/rawmodel-utils/src/helpers/is-class-of.ts
100.00% <ø> (ø)

...kages/rawmodel-utils/src/helpers/is-instance-of.ts
100.00% <ø> (ø)

packages/rawmodel-utils/src/helpers/normalize.ts
87.50% <ø> (ø)

packages/rawmodel-utils/src/helpers/to-array.ts
100.00% <ø> (ø)

packages/rawmodel-utils/src/helpers/to-boolean.ts
100.00% <ø> (ø)

...ckages/rawmodel-validators/src/validators/match.ts
83.33% <0.00%> (ø)

packages/rawmodel-utils/src/helpers/to-integer.ts
87.50% <50.00%> (ø)

...awmodel-validators/src/validators/string-length.ts
82.60% <50.00%> (ø)

...ckages/rawmodel-utils/src/helpers/is-deep-equal.ts
87.50% <66.66%> (-12.50%)
:arrow_down:

... and 17 more


Solid v1.7

This PR shows the upcoming changes for Solid 1.7. You can try it out on thenext branch of git and beta tag on npm. It has numbering like v1.7.0-beta.3.
This release has a lot of TypeScript breaking changes. We've been pretty lenient on TS breaking changes in minors so we are keeping that trend, but I'm particularly concerned with this one. So I'd appreciate the ecosystem to try it out and give some feedback leading up to the release. On the positive all the TS fixes will be backwards compatible. We've just gotten more strict with the JSX mostly, so bending to that won't break any older versions of Solid.
I will publish beta versions of related packages (like vite-plugin-solid) so that you can try this. Most packages should just work with their latest versions.

41 errors in SUID  due to https://github.com/solidjs/solid/discussions/1554.

@juanrgm this is expected. solid-headless is also going to be affected by this

Yeah to clarify I'm expecting a bunch of errors as this is stricter. It is more trying to determine if there is any truly awkward pieces. I don't think the errors effect external facing APIs.. just internals of libraries or applications themselves.


Reduce console output in PrimitiveParserPerfTests

As it stood, each perf test would spew out 1000 lines of fairly useless text to the console. This change removes this console output and replaces it with a single line expressing the name of the test as well as the string argument passed to it.

@KrzysztofCwalina PTAL


Update release pipeline with new AWS role and parameter store key

We renamed the release pipeline from Test Splitter - Release to Test Engine Client - Release. This breaks the AWS authorization because the role that was used in the pipeline is scoped with the pipeline slug. This PR updates the release pipeline configuration with the new AWS role that is scoped with the new pipeline slug.

Nice catch!


Forecast not properly reporting current temperature.

$ forecast

--- Berlin, Germany ------------------------------------------------------------

    19° Partly cloudy until evening.

Tue 18° Drizzle starting in the evening.
Wed 21° Mostly cloudy throughout the day.
Thu 23° Mostly cloudy throughout the day.
Fri 23° Drizzle in the morning.
Sat 24° Partly cloudy throughout the day.
Sun 23° Partly cloudy throughout the day.
Mon 20° Drizzle in the afternoon.

Drizzle tomorrow through Monday, with temperatures rising to 24°C on Saturday.

Now you are prepared.

19° C. Currently it is 15°C though, which forecast correctly reports when using the --hourly-switch:
forecast --hourly

--- Berlin, Germany ------------------------------------------------------------

Today

7pm  15° Partly Cloudy

[...]

Maybe it would be possible to report the current conditions when using forecast sans --hourly-switch?

I agree, because I'm inside, at work, with no windows, when I check the weather. I'm not going outside to check the weather... I need to check it first so I know if I need to bring my coat. When I type forecast I expect to see current conditions as the first line. Then the line with the high and summary for today (which is currently the first line).
That said, it's easy enough to create aliases or extend this tool to behave like I want it to. Everybody is probably going to want something different.


Example and Further Documentation for Compression of Point Clouds

It would be great to have an example for the compression of point clouds, especially programmatically in three.js. Do point clouds stay as PLY files? Or are they converted to another file type? Also I know in Blender when you import with PLY you can export as a GLTF with Loose Vertices turned on and this is very efficient in file size. Does meshopt convert the PLY to GLTF as well?

glTFPack can take in a standard glTF file, containing point primitives, and then output a glTF or gib containing compressed point primitives.
This effectively gives you MeshOpt compressed point-clouds.
some details here: https://github.com/wallabyway/minimal-pointcloud-gltf

Yup, maybe to expand on this:

meshoptimizer-the-library provides a few different algorithms that, when put together, allow to optimize point cloud transmission and storage
gltfpack can process .gltf files with these algorithms
gltfpack does not support PLY files as an input; I looked into this briefly a couple years ago and the conclusion was that the format is fairly niche, there are not that many solid existing libraries to parse it, and overall this would not be too important

https://github.com/zeux/meshoptimizer#point-cloud-compression section specifically (which maybe this is talking about?) is documenting the algorithms that already exist in meshoptimizer and already used by gltfpack. Looks like this is not documenting meshopt_simplifyPoints (which is also used by gltfpack), so I'll fix this.
These algorithms are currently not exposed to JS, so if a JS program gets its input as a point cloud, JS meshoptimizer modules can't be used to optimize it. I'm not sure if this is what the question is, as if you use glTF files already then this isn't relevant.

Updated gltfpack README https://github.com/zeux/meshoptimizer/commit/82888a1e9b65df43abfe3f3dbf462b78711014e8 to mention point cloud processing more explicitly and updated gltfpack's command line help to make it clearer that -si also applies to point clouds. I don't want to document meshopt_simplifyPoints for now as it's experimental and fairly likely to change the interface to support colors, as well as the implementation to use a different algorithm in the future.


feat: 3 more audit-secureblue checks

Tested on a regular install of a secureblue Silverblue image, unsure if the hardened_malloc check is what was requested.

P.S.: apologies for the lack of communication. This closes issues #401 #402 #403 and #404


How to filter a collection by datetime?

I have an endpoint that returns Post objects which have collections of PostComment objects, both of which have property LastModifiedDateTime of type DateTime.
I am trying to query this endpoint by either Post/LastModifiedDateTime  OR PostComment/LastModifiedDateTime  with operator ">" and a specific datetime.
The URL query that accomplishes this looks like:
https://localhost:44302/odata/Posts?$expand=PostResources,PostComments&$filter=(LastModifiedDateTime gt 2017-04-21T05:54:15.167Z) or (PostComments/any(c: c/LastModifiedDateTime gt 2017-04-21T05:54:15.167Z))&$orderby=CreatedDateTime desc
I am having trouble writing Predicates that accomplish this in angular code.
var predicates = [];
var unreadPost = new $odata.Predicate("LastModifiedDateTime", ">", new $odata.Value(syncService.postSeenDateTime, "DateTimeOffset"));
predicates.push(unreadPost);
// how to write predicate for 'any' of the nested LastModifiedDateTime gt than a date here ?
filter = $odata.Predicate.or(predicates);
var posts = context.odata()
.expand("PostResources")
.expand("PostComments")
.filter(predicates )
.orderBy("CreatedDateTime", "desc");

var end = new $odata.Predicate('LastModifiedDateTime', '<=', new $odata.Property(endDate));
var combination = $odata.Predicate.and([start, end]);

context.odata()
.expand("PostResources")
.expand("PostComments")
.filter(combination)
.orderBy("CreatedDateTime", "desc");


[PoC] migrate to go module, alternative

Alternative to https://github.com/lyft/flyteidl/pull/27

@wild-endeavor PTAL

Downside of this approach is one can not run go mod tidy under boilerplate/lyft/golang_support_tools/, because that removes everything.


Image file name

Some releases before image file name changed and doesn't display disk letters (C:\ , D:) Is it bug or feature? :-) In browser i like it display with old way, in detail it can stay.

It's a regression bug. It'll be fixed when I get back from holidays 👍


Bump capi to v1.6.0 and cert-manager to v1.13.2

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


HTML code generated to include a SVG is broken

Expected Behavior
I'm trying to add a SVG image from creativecommons.org. I want to have this SVG image inserted with a link to the website.
Current Behavior
The HTML code generated by jekyll adds 2 tags at the wrong place (
) and break the HTML code consistency: a  appear and the link doesn't work.

Possible Solution
Don't know. I'm new to Jekyll. Perhaps it's my bad, perhaps it's the SVG, perhaps a bug related to minima template, or perhaps it's the HTML generator used by Jekyll.
Steps to reproduce

Download the svg file in _includes folder
create a snippet icon-cc-by-nc-sa_bug.html in the _includesfolder with following code:

{% include by-nc-sa.svg %}

create a post with the following code:

---
layout: post
title:  "Test du bug SVG"
date:   2016-09-18 00:12:00 +0000
categories: bug
---
{% include icon-cc-by-nc-sa_bug.html %}

build with jekyll

Your environment
GEM
  remote: https://rubygems.org/
  specs:
    colorator (1.1.0)
    ffi (1.9.14)
    forwardable-extended (2.6.0)
    jekyll (3.2.1)
      colorator (~> 1.0)
      jekyll-sass-converter (~> 1.0)
      jekyll-watch (~> 1.1)
      kramdown (~> 1.3)
      liquid (~> 3.0)
      mercenary (~> 0.3.3)
      pathutil (~> 0.9)
      rouge (~> 1.7)
      safe_yaml (~> 1.0)
    jekyll-sass-converter (1.4.0)
      sass (~> 3.4)
    jekyll-watch (1.5.0)
      listen (~> 3.0, < 3.1)
    kramdown (1.12.0)
    liquid (3.0.6)
    listen (3.0.8)
      rb-fsevent (~> 0.9, >= 0.9.4)
      rb-inotify (~> 0.9, >= 0.9.7)
    mercenary (0.3.6)
    minima (1.2.0)
    pathutil (0.14.0)
      forwardable-extended (~> 2.6)
    rb-fsevent (0.9.7)
    rb-inotify (0.9.7)
      ffi (>= 0.5.0)
    rouge (1.11.1)
    safe_yaml (1.0.4)
    sass (3.4.22)

PLATFORMS
  ruby

DEPENDENCIES
  jekyll (= 3.2.1)
  minima

RUBY VERSION
   ruby 2.3.1p112

BUNDLED WITH
   1.13.0

This issue is not due to bug in minima. You made a mistake while pasting the svg code. Please recheck your html file. If you cant resolve it, simply redo adding the SVG on a fresh copy of the html file.

This issue is not due to a bug in minima. The SVG file contains unnecessary data embedded by Inkscape. You can remove that data using svg cleaner tools. One such tool online is kraken.io

thanks for the reply, I found this workaroud in the mean time. Question now: Is it normal and we close the issue or do I assign it to jekyll or perhaps a module used for the html generation?

you can close this issue as its not related to minima. Regarding, the second part of your question, I'll ping @pathawks.

@oncelben31 Yeah, this seems to be a Jekyll issue.
If you open an issue over there and mention me, I will look into it.

transfered to https://github.com/jekyll/jekyll/issues/5438


Keyboard events issue

I'm not sure if that's SDL or of this project, bug, but:
On Linux/Ubuntu, when you start application with unicode keyboard layout, KEYUP/KEYDOWN events contain keycodes (both sym and scancode) which are >256, even if you change layout while application is running. However if you run application having english layout selected, even if you change layout, you only get codes <256 in KEYUP/KEYDOWN. That leads to errors when sometimes your input is going to screen of the device 2 times per key press, and sometimes - 0 times.
TEXT events contain right symbols, so prefer-text would be good workaround.
@rom1v do you handle this SDL thing correctly? Is that their known behavior?
$ sdl2-config --version
2.0.8

However if you run application having english layout selected, even if you change layout, you only get codes <256 in KEYUP/KEYDOWN.

For keycodes, it seems expected:
https://github.com/spurious/SDL-mirror/blob/66e0e5ad0d554d88d58b92c4ba70d1e4b2f98282/include/SDL_keycode.h#L47-L48
https://github.com/spurious/SDL-mirror/blob/66e0e5ad0d554d88d58b92c4ba70d1e4b2f98282/include/SDL_keycode.h#L154

do you handle this SDL thing correctly

scrcpy just receives the SDL key events SDL_KEYUP and SDL_KEYDOWN:
https://github.com/Genymobile/scrcpy/blob/0be766e71a30eec1709da7b24999b6df2b40dc65/app/src/scrcpy.c#L200-L204

@rom1v I'm not about that thing, I see here that SDL application sticks to that keyboard layout with which it was started o_O, for KEY events, if I start with Russian then I receive Russian unicode characters no matter how I change it during that run of the application. This is totally unexpected, and good thing is that normally KEY events are not used for text processing.

I see here that SDL application sticks to that keyboard layout with which it was started o_O, for KEY events, if I start with Russian then I receive Russian unicode characters no matter how I change it during that run of the application.

Yes, when I wrote "scrcpy just receives the SDL key events SDL_KEYUP and SDL_KEYDOWN", I meant that scrcpy just react to what SDL sends. So if SDL does not react to keyboard layout changes, I'm not sure scrcpy could do something.
Ref: #1729

I guess we shall never process text characters in input_manager_process_key in order to have consistent behavior :man_shrugging: No matter prefer-text is set or not.

@rom1v I guess we can tune SDL somehow. For example for X11 they call X11_UpdateKeymap in order to load keymap from X11 to SDL. It's likely that this method is just skipping being called for some reason, when user switches his keymap. It can be scrcpy bug, really.


Your sphinx documentation is not working

I am trying to run r-kernel thebe. So I came up to your site. However, your own documentation is giving me the same error I am currently facing:
NameError: name 'library' is not defined

Although you have specified an R kernel, it is running on Jupyter... Any ideas or workarounds would be highly appreciated

thanks for noticing - closing this one as a duplicate of:

https://github.com/executablebooks/sphinx-thebe/issues/43


Use existing buildworld result from base system

I build my own source tree and think it'd be a good idea to be able to have the option to have cbsd installworld install from this tree, instead of having to do a separate buildworld for cbsd nodes.

Good idea.
Currently you can use buildworld from local machine only by hands, e.g from /usr/src:
mkdir ~cbsd/basejail/base_`uname -m`_`uname -m`_`uname -r|cut -d - -f 1`
make -C /usr/src installworld DESTDIR=~cbsd/basejail/base_`uname -m`_`uname -m`_`uname -r|cut -d - -f 1`

and apply some CBSD-specific post-install action:
cbsd preparebase dst=~cbsd/basejail/base_`uname -m`_`uname -m`_`uname -r|cut -d - -f 1`

on my system (FreeBSD 11 amd64)
~cbsd/basejail/base_`uname -m`_`uname -m`_`uname -r|cut -d - -f 1`

extracted to /usr/jails/basejail/base_amd64_amd64_11.0
And yes, perhaps it makes sense to me to make this operation separate command.
So i've leave this issue in open state for next release.
PS: On the other hand, you can setup your own repo for base.txz and change repo source from http://www.bsdstore.ru to yours for other nodes.

(within 79c51fe ): Implement populate base from current system. No source tree or object file needed. This work only if the version of container == base system version


Issue 305 broken link because of language fixes

Motivation
Second attempt to fix https://github.com/facebook/Docusaurus/issues/305
Fixed some bugs in the first PR. Tested many rounds in translation enabled/disabled cases.
Test Plan

website without translation.

docusaurus-init
npm run start
check site
npm run build
cd build
python -m SimpleHTTPServer 5000
check site

website with translation.

docusaurus-init
npm run examples translations
npm run start
check site
npm run build
cd build
python -m SimpleHTTPServer 5000

Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

Have you tested the GitHub versioning and page export? I have no idea how to test that bit myself.

@neilsutcliffe I actually don't know what exactly are those. I haven't touched versioning part yet.

@neilsutcliffe I believe this PR, while touching versioning a little bit through some refactoring, does not affect versioning in any meaningful way. That said, I can run npm run version to test that out too. And by "page export", do you mean just building the static HTML assets so you can place them on any web server of choice? Like what is done via npm run build.

Did a round test on Docusaurus site. Look good. Except one thing, after npm run build. If I run local python SimpleHTTPServer at build/ dir, assets would not load. I need to go into build/Docusaurus/  to run server. Is this expected?

@richardzcode I am testing this PR out now. Thanks!

I'm having a read up on Versioning now. It will be useful to know.

Well that would be testing deployment I guess. Can a docker container do that?

@richardzcode I am running the Docusaurus site locally too. It is looking good. One thing your PR adds to our site is the translation dropdown.

vs. what is on docusaurus.io now.

I am initially thinking that this is a good thing since we do have translations enabled with a languages.js file. We just happen to support only one language at this time.

@richardzcode

Except one thing, after npm run build. If I run local python SimpleHTTPServer at build/ dir, assets would not load. I need to go into build/Docusaurus/ to run server. Is this expected?

That's a good point. Yes, you need to go into the $projectName directory to run the site locally from the build files. That is admittedly not very clear in the docs. And begs the question whether we really need to output the $projectName when building to begin with.

I like it. Even if it only has one option. If the presence of a language file can determine if languages are available, then that is a win for convention!

@richardzcode This is looking good. I have done testing on both the examples site from docusaurus-init or npm run examples as well as a local version of docusaurus.io, and things seem to be working fairly well.
There might be a few updates I make after we land this, but all in all, this should probably be our direction.
Thinking about this -- this could theoretically be a breaking change for some sites depending on how they have their index.js page implemented. But this may not affect most of our sites since they set the language to en anyway.

Yeah I thought too showing dropdown was good even if only one language enabled. But it can be both ways. To keep consistent let's hide it.

@richardzcode That's fair for now. But I might bring it back even for only one language :) I think I like the relationship of:
langauges.js exists => translations enabled => dropdown shown.
We could also have a config option called hideTranslationDropdown that forces the translation dropdown to be hidden. But I am not sure yet if that's a good idea or not.

There is also logic in headerNav that allows you to add a language box using the siteConfig.js but I'm guessing that should never be used?

@neilsutcliffe Hi.

There is also logic in headerNav that allows you to add a language box using the siteConfig.js but I'm guessing that should never be used?

links is based upon the headerLinks config in siteConfig.js with added information pushed to it.
e.g., in HeaderNav.js
renderResponsiveNav() {
    const headerLinks = this.props.config.headerLinks;
    // add language drop down to end if location not specified
    let languages = false;
    headerLinks.forEach(link => {
      if (link.languages) {
        languages = true;
      }
    });
    if (!languages) {
      headerLinks.push({languages: true});
    }

And the code you referenced is the only code where we render the LanguageDropDown.
So it is used all the time :)
@richardzcode could have, I suppose, put his checks there instead of directly in render() method of the LanguageDropDown component.

right. the check is better to be outside. keep the logic of hiding dropdown for one language for now.

I just left a massive pull-request, which I don't expect to get approved for sometime, if at all that relates a bit to this issue.
#326

@richardzcode I am going to try this merge again. :) I did testing on the test site and the Docusaurus site. All seemed pretty well, modulo some small changes that I will make afterwards.
@neilsutcliffe You many want to rebase #326 after this lands, assuming I don't have to revert it for whatever reason.

Ok, here we go. :)

https://docusaurus.io seems functional \o/

In this comment, I will list some auxiliary commits that I am going to make associated with this:

Thank you @JoelMarcey !
For potential breaking of some sites. What I can think of is to create both default pages and 'en' pages.
In generate.js, after
    const docComp = (
      <DocsLayout metadata={metadata} language={language} config={siteConfig}>
        {rawContent}
      </DocsLayout>
    );
    const str = renderToStaticMarkup(docComp);

    let targetFile = join(buildDir, metadata.permalink);

add something like
    if (!env.translation.enabled) {
      // generate 'en' pages too
      targetFile = targetFile.replace('/docs/', '/docs/en/');
      writeFileAndCreateFolder(targetFile, str);
    }

But not sure if it is worth it. I personally would rather let user correct their index pages, since most of the users are just starting out.

I'm not sure about rebasing, but I merged the previous version of this PR (and will merge in the latest master too).
Obviously I had a lot of conflicts, but I'm in the right space to deal with them.


M3-78 User Notification Menu

@alioso Could reduce the height of the menu, and have it compensate for the scrollbar width


Make dependencies on download page kts-friendly

Description
Added braces to dependency declarations on the Downloads page to make them copy-paste friendly for kts build scripts
...
Check list

[X] I have updated CHANGELOG.md if required.
[X] I have updated documentation if required.

Thank you @zsmb13!


Feature request: Add syntax sugar for dictionary access

Hey there, first, thank you very much for the project, it is quite handy for me.
What do you think of being able to use ? on dictionaries access?
So instead of writing this:
let data = @[
    a: 1
]
function get_value_by_key(key)
    data[key]
end

function get_value()
    get_value_by_key("b")
end

std.print(std.catch(get_value))

one could write this:
let data = @[
    a: 1
]

function get_value()
    data["b"]?
end

std.print(get_value())

Sounds like a great feature for me! But I believe we'll have to use another symbol instead of ?, as that one is already used. Perhaps something like:
let data = @[ a: 1 ]
std.assert(data:a == 1)
std.assert(data:["a"] == 1)
std.assert(data:a:b == nil)
std.assert(data:["c"]:["d"] == nil)

Does that seem reasonable to you?

@gahag makes sense to me!
we could also go with :- to keep consistency with Bash :-)

@gahag makes sense to me!
we could also go with :- to keep consistency with Bash :-)

@gahag sure, either way would be nice. I thought of ? because it could also short circuit functions


DBZ-2978 Adding Syntax Highlighter(hljs)

Excellent, thx! Can you push this to staging, please?

Excellent, thx! Can you push this to staging, please?

Excellent, thx! Can you push this to staging, please?

Already pushed on staging https://debezium-builder.github.io/blog/2019/02/19/reliable-microservices-data-exchange-with-the-outbox-pattern/

Excellent, thx! Can you push this to staging, please?

Already pushed on staging https://debezium-builder.github.io/blog/2019/02/19/reliable-microservices-data-exchange-with-the-outbox-pattern/

Ok, nice overall. There's one issue with call-outs still. E.g. look here:
https://debezium-builder.github.io/blog/2019/10/01/audit-logs-with-change-data-capture-and-stream-processing/
In the second listing, (1), (2), etc. should be rendered using those bubble
icons, as (4), (5), (6) below the listing. Same for the explanations 1 - 3
for those call outs. It works for 4 - 6, as I manually added them there,
instead of relying on the default call-out mechanism (look at the AsciiDoc
source to see what I mean).

Ok, nice overall. There's one issue with call-outs still. E.g. look here:
https://debezium-builder.github.io/blog/2019/10/01/audit-logs-with-change-data-capture-and-stream-processing/
In the second listing, (1), (2), etc. should be rendered using those bubble
icons, as (4), (5), (6) below the listing. Same for the explanations 1 - 3
for those call outs. It works for 4 - 6, as I manually added them there,
instead of relying on the default call-out mechanism (look at the AsciiDoc
source to see what I mean).

Pushed on staging for testing https://debezium-builder.github.io/blog/2019/10/01/audit-logs-with-change-data-capture-and-stream-processing/ and updated the PR

Pushed on staging for testing https://debezium-builder.github.io/blog/2019/10/01/audit-logs-with-change-data-capture-and-stream-processing/ and updated the PR

Hum, hum, interesting. So is this used at build time then? I.e. with that
script being present, if you have JS disabled in the browser, will the
outcome be the same as with JS enabled?

Hum, hum, interesting. So is this used at build time then? I.e. with that
script being present, if you have JS disabled in the browser, will the
outcome be the same as with JS enabled?

Hum, hum, interesting. So is this used at build time then? I.e. with that script being present, if you have JS disabled in the browser, will the outcome be the same as with JS enabled?
…

I think it find some matching tags and add css to it. Outcome will be little different if JS is disabled in the browser. It might look like first screenshort(without highlight.js)

Hum, hum, interesting. So is this used at build time then? I.e. with that script being present, if you have JS disabled in the browser, will the outcome be the same as with JS enabled?
…

I think it find some matching tags and add css to it. Outcome will be little different if JS is disabled in the browser. It might look like first screenshort(without highlight.js)

We might show some warning if JS is disabled. WDYT?

We might show some warning if JS is disabled. WDYT?

@uidoyen, taking a step back. What was behavior before the migration; was high-lighting purely server-side back then? I pushed tags develop-website-pre-migration and master-website-pre-migration back then, so you could take a look. If it was purely server-side (which I always assumed), I'd prefer to stick to that.

@uidoyen, taking a step back. What was behavior before the migration; was high-lighting purely server-side back then? I pushed tags develop-website-pre-migration and master-website-pre-migration back then, so you could take a look. If it was purely server-side (which I always assumed), I'd prefer to stick to that.

@uidoyen, taking a step back. What was behavior before the migration; was high-lighting purely server-side back then? I pushed tags develop-website-pre-migration and master-website-pre-migration back then, so you could take a look. If it was purely server-side (which I always assumed), I'd prefer to stick to that.

I checked the tags, actually it wasn't purely server-side earlier, it was using highlight.js as well.

@uidoyen, taking a step back. What was behavior before the migration; was high-lighting purely server-side back then? I pushed tags develop-website-pre-migration and master-website-pre-migration back then, so you could take a look. If it was purely server-side (which I always assumed), I'd prefer to stick to that.

I checked the tags, actually it wasn't purely server-side earlier, it was using highlight.js as well.

Ok, gotcha! Will apply then. Thanks!

Ok, gotcha! Will apply then. Thanks!


Add module to adjust the icon theme colors

I've been using this in my personal configuration for a bit, but not sure if you guys will be interested in this. The script is a modified and stripped down version of  color-manager.
One issue that I'm having is with parent themes. They should always be accessible in propagatedbuildinputs, but I'm unsure how to dynamically adjust them. Additionally, this script could potentially be expanded to recolor wallpapers, but that would require some adjustments as well.
Examples:
Gruvbox:

Nord:

if were going to add a new package to stylix we might want to reorganise were it and the palate generator are place, ie putting them both into ./pkgs or something

I think this needs some tweaking

I'm wondering how we should add support for recoloring thw wallpaper as well? @danth

After #102 is finished we should be able to add that as a function which takes in an image and a color scheme, and outputs the recoloured wallpaper.

@danth What about recoloring the parent icon themes? For example in the "Numix Circle" theme the folder icons come from the parent "Numix" theme and those don't get recolored and look out of place. Surely there's a way?

I'm not too familiar with how icon themes are packaged in NixOS. If the parent theme is a separate package then we would need to override it from there. Does the Numix Circle theme depend on Numix or do you install them separately?

@danth https://github.com/NixOS/nixpkgs/blob/nixos-23.05/pkgs/data/icons/numix-icon-theme-circle/default.nix#L40
Every parent theme that the child theme inherits from should be part of propagatedBuildInputs

If they're the only thing in propagatedBuildInputs you could map the override function over that as part of the override

If they're the only thing in propagatedBuildInputs you could map the override function over that as part of the override

Could you help me with that? I'm not quite sure how

Any example configs on how to use this branch? The icon theme colors look great.

@donovanglover
stylix.targets.iconTheme = {
enable = true;
name = "Zafiro-icons-Dark";
package = pkgs.zafiro-icons;
recolor = {
enable = true;
mode = "palette"; # "color" "color-from-palette" "palette"
colors = with config.lib.stylix.colors.withHashtag; [
base00
base01
base02
base03
base04
base05
base06
base07
base08
base09
base0A
base0B
base0C
base0D
base0E
base0F
];
smooth = false;
};
};

@danth I added lots of options to better allow for adjusting the output, which helps icons that previously had very poor contrast when they got recolored

When rebased on master, this branch causes an infinite recursion with my config:
error:
       … while calling the 'head' builtin

         at /nix/store/gzv0nsm8d5js3wzq2mr1sv9lfp1iyail-source/lib/attrsets.nix:960:11:

          959|         || pred here (elemAt values 1) (head values) then
          960|           head values
             |           ^
          961|         else

       … while evaluating the attribute 'value'

         at /nix/store/gzv0nsm8d5js3wzq2mr1sv9lfp1iyail-source/lib/modules.nix:809:9:

          808|     in warnDeprecation opt //
          809|       { value = builtins.addErrorContext "while evaluating the option `${showOption loc}':" value;
             |         ^
          810|         inherit (res.defsFinal') highestPrio;

       (stack trace truncated; use '--show-trace' to show the full trace)

       error: infinite recursion encountered

       at /nix/store/gzv0nsm8d5js3wzq2mr1sv9lfp1iyail-source/lib/modules.nix:233:21:

          232|           (regularModules ++ [ internalModule ])
          233|           ({ inherit lib options config specialArgs; } // specialArgs);
             |                     ^
          234|         in mergeModules prefix (reverseList collected);

@danth Could it be related to 53d1bb4007589157ab9d873a33217183dc60c00c?

Got around to trying this out and it's pretty cool. Lots of options to play around with but would be great if it produced better results by default.
Not all themes will have propagatedBuildInputs so it shouldn't fail for those themes. I also had a few cases where certain icons would end up as circles with a single color, like the NixOS Manual for example.

Anyone interested in this may also want to check #370, where I implemented this manually for parts of the Adwaita icon theme (the default in GNOME)

@donovanglover I made some changes, it should not produce circles of indistinguishable anymore (or so I hope)


impossible to update VSCODE with standard user on Macos

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.74.1
OS Version: MacOS 13.2 (22D49)

Steps to Reproduce:

install VScode for a standard user.
when an update is pushed, user is prompte to update VSCode by setting Admin Credential

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.75.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Also for note when this issue is triaged:
In discussions on this scenario, I initially thought the issue could be https://github.com/microsoft/vscode/issues/115805, though they shared there seems to be nothing unusual about their permissions.

already check that article. and not the same

Yes, that was my understanding too, thanks for confirming!
When you get a chance, could you share if there are special enterprise circumstances / setup here (i.e. is anything managed or automated by your company)?

Can you delete the ShipIt_Stderr* and ShipIt_stdout* files as they are owned by root and has 0644 as permission which would disallow update initiated from your User  to not have write access to these logs causing the above prompt.

@bamurtaugh
devices are prepared by our MDM, we are just decresing the user as Standard.
all Apps are install via Munki. no nothing special, i would say
@deepak1556 it's done but same messsage.... request admin right
by the way ShipIt_Stderr* and ShipIt_stdout*  are logs i do not think they are used in the process

@LorealEndPoint the logs need to be writable by the update process otherwise there was an issue were updates cannot be applied, refs https://github.com/Squirrel/Squirrel.Mac/pull/255 but that has been addressed in the runtime. Can you attach the generated logs for your scenario.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Atomics!

The one we've all been waiting for~
Things that are missing/wrong here:

[ ] some extend bits. all r/e here was done by hand (i.e. without tools), so it's hard to get those
[ ] 64-bit integer atomics. I couldn't get them to work on my version of macOS
[ ] float atomics. these need macOS 13 but if I upgrade my r/e setup is going to break

I'd appreciate if someone else could fill in those gaps
Closes #2

Looks like the extension bits for AtomicDestinationDesc were at 40:41 (0001-Atomic-op-register-extensions.patch).  Were there any other extension bits you were missing?
Also, atomic threadgroup destinations were breaking because they didn't have a mask register.  I did an if/else on self.is_optional (since it's also used only by the atomic version) but you might want to add a separate flag for it.
For floats, at least on M1 they compile to a cmpxchg loop.  Maybe they have instructions for it on M2.

Test Input/Output
kernel void yay(uint u [[thread_position_in_grid]], device atomic_float* a) {
	atomic_fetch_add_explicit(a + u, 2.0f, memory_order_relaxed);
}

   0: 72051004             get_sr           r1, sr80 (thread_position_in_grid.x)
   4: 0519200e00c01200     device_load      0, i32, x, r3, u0_u1, r1, unsigned
   c: 3800                 wait             0
   e: 62000000             mov_imm          r0l, 0
  12: 2a8946020001         fadd32           r2, r3, 2.0
  18: d528208e00d00400     atomic           cmpxchg, 0, r5, u0_u1, r1, unsigned, r2, 1, 0, 1, 20
  20: 3800                 wait             0
  22: 92098a622c010190     icmpsel          seq, r2.cache, r5.cache, r3.discard, 1, 0
  2a: 7e0dca0a8000         mov              r3, r5.discard
  30: 5294c4000000         while_icmp       r0l, seq, r2l.discard, 0, 2
  36: 00c0dcffffff         jmp_exec_any     0x12
  3c:<PHONE_NUMBER>00         pop_exec         r0l, 2
  42: 8800                 stop

For 64-bit integers, there's only one operation currently supported by Metal's frontend, atomic_max_explicit (or min) on device atomic_ulong*s, and it ICEs the M1 backend compiler.
kernel void yay(uint u [[thread_position_in_grid]], device atomic_ulong* a) {
	atomic_max_explicit(a + u, 10, memory_order_relaxed);
}

→ Compiler encountered an internal error
Also, while testing, it looks like there's some sort of lsl-like field in the threadgroup_(load|store) instructions, but they use 1, 2, and 4 instead of 0, 1, 2... Maybe someone should try sticking non-powers-of-two in that field and see what happens.

  Instead, if you pair up the current O field with bits 40:42, you get [0, 1] [1, 1] [1, 2] [3, 1] [1, 4] [5, 1] [3, 2]...
They make the correct offsets if you multiply the two together, but the compiler only ever puts powers of two into the 40:42 field...

Looks like the extension bits for AtomicDestinationDesc were at 40:41 (0001-Atomic-op-register-extensions.patch). Were there any other extension bits you were missing?

Awesome -- confirmed with Mesa. I was wondering if maybe the atomic source was split into 6-2 like the destination, but seemingly the contiguous 8 bits works (as in, tests are passing with it contiguous and high bits used, so 🤷♀ ) Thank you!

For floats, at least on M1 they compile to a cmpxchg loop.

Delightful 🤣 Fair enough, thanks. Makes you wonder why they bothered putting it in metal.

→ Compiler encountered an internal error

Truly, delightful 🤣

I think Apple added some extra atomic instructions to M2, to support Nanite and float atomics. I got an unconfirmed DM that Apple added it to M2 and not other Apple 8 GPUs. More info: https://forums.unrealengine.com/t/lumen-nanite-on-macos/508411/54?u=philipturner. Not a single volunteer owned an M2 GPU and could confirm whether it worked.

For floats, at least on M1 they compile to a cmpxchg loop. Maybe they have instructions for it on M2. ~Really makes you wonder why float atomics aren't supported on <Apple7 GPUs, if they were going to polyfill it anyways (or whatever the term is for doing that to an instruction)...~ Edit: It's probably the simd_fadd that they use when you target a constant address.
  0: 72051004             get_sr           r1, sr80 (thread_position_in_grid.x)
  4: 0519200e00c01200     device_load      0, i32, x, r3, u0_u1, r1, unsigned
  c: 3800                 wait             0
  e: 62000000             mov_imm          r0l, 0
 12: 2a8946020001         fadd32           r2, r3, 2.0
 18: d528208e00d00400     atomic           cmpxchg, 0, r5, u0_u1, r1, unsigned, r2, 1, 0, 1, 20
 20: 3800                 wait             0
 22: 92098a622c010190     icmpsel          seq, r2.cache, r5.cache, r3.discard, 1, 0
 2a: 7e0dca0a8000         mov              r3, r5.discard
 30: 5294c4000000         while_icmp       r0l, seq, r2l.discard, 0, 2
 36: 00c0dcffffff         jmp_exec_any     0x12
 3c:<PHONE_NUMBER>00         pop_exec         r0l, 2
 42: 8800                 stop

Could someone explain to me how this code works? I have trouble wrapping my head around it. So at 4 the value from `[a+u]` is being loaded into `r3`, incremented by 2 (with result stored in `r2`) in 12, and then we have a compare+exchange at 18, followed by a footer where presumably a new  (in case of conflict) value is loaded into `r3`, and then we go back to the addition.

But I am confused about the `cmpxchg` line. I see the address (`u0_u1, r1`) and what to write on success (`r2`), but where is the value to be compared with? I'd expect there to be a mention of `r3` somewhere as it's the value we want to ensure is still in memory when we do the atomic swap? What am I missing?

Yeah, you're correct. The disassembly isn't quite correct for cmpxchg. There's a comment in the patch:
	# unusual, uses register pair for old/new value
	3: 'cmpxchg',

r2 should be disassembled as r2_r3 (i.e. the "what to compare" register is always the next register after the "what to write on success" register)

Ah, I was wondering what that comment meant. Got it, thanks for explanation!

Looks like it is indeed supported on M2
Can't actually run these, but I used metal-nt to compile for applegpu_g14g and it seems to work
#include <metal_stdlib>
using namespace metal;
kernel void yay(uint u [[thread_position_in_grid]], device atomic_ulong* a, device atomic_uint* b) {
	atomic_max_explicit(a + u, 10, memory_order_relaxed);
	atomic_max_explicit(a, 10, memory_order_relaxed);
	atomic_max_explicit(a + 1, 10, memory_order_relaxed);
	atomic_max_explicit(reinterpret_cast<device atomic_ulong*>(b + u), 1, memory_order_relaxed);
	atomic_min_explicit(reinterpret_cast<device atomic_ulong*>(b + u), 1, memory_order_relaxed);
	uint expected = 0;
	atomic_compare_exchange_weak_explicit(b + u, &expected, expected + 1, memory_order_relaxed, memory_order_relaxed);
}

   0: f2191004             get_sr           r6.cache, sr80 (thread_position_in_grid.x)
   4: fe0180098000         mov              r0.cache, u0
   a: fe0582098000         mov              r1.cache, u1
  10: 620d00000000         mov_imm          r3, 0
  16: 0e13c0c3a4001000     iadd             r4_r5, r0_r1.discard, r6, lsl 3
  1e:<PHONE_NUMBER>00         mov_imm          r1, 0
  24: 62090a000000         mov_imm          r2, 10
  2a:<PHONE_NUMBER>00         mov_imm          r0, 1
  30: d500088500700400     atomic           cmpxchg, 0, None, r4_r5, 0, signed, r2, 1, 0, 1, 112
  38: d500008d00700400     atomic           cmpxchg, 0, None, u0_u1, 0, signed, r2, 1, 0, 1, 112
  40: d500208d00700400     atomic           cmpxchg, 0, None, u0_u1, 2, signed, r2, 1, 0, 1, 112
  48: d500c48e00700000     atomic           cmpxchg, 0, None, u2_u3, r6, unsigned, r0, 1, 0, 1, 112
  50: d500c48e00300000     atomic           cmpxchg, 0, None, u2_u3, r6, unsigned, r0, 1, 0, 1, 48
  58: d500c48e00500000     atomic           cmpxchg, 0, None, u2_u3, r6, unsigned, r0, 1, 0, 1, 80
  60: 8800                 stop

I don't think our signed/unsigned bit is correct here, it seems to be getting used for something else
Kind of curious what would you would get if you enabled the 32-bit output register on one of these, but I don't have an M2 to try it...

For anyone who wants to try this themselves
If the metal code is saved into test.metal and the following json is in desc.mtlp-json...
{
	"pipelines": {
		"compute_pipelines": [
			{
				"compute_function": "yay"
			}
		]
	}
}

xcrun metal test.metal -o test.metallib
xcrun metal-nt -arch applegpu_g14g test.metallib -N desc.mtlp-json -o test-m2.metallib
python3 compiler_explorer.py test-m2.metallib

We got someone with an M2 Max who might test it out soon - I'll hyperlink this which will have the latest info.

I don't think our signed/unsigned bit is correct here, it seems to be getting used for something else

Is it just that my choice of name/syntax is terrible? signed and unsigned come from the Ou (offset unsigned) bit, and indicate whether the preceding operand (the address offset) is sign or zero extended from 32-bit to 64-bit before being added to the address. Arm writes this as LDR X0, [X0, W1, UXTW] vs LDR X0, [X0, W1, SXTW], which doesn't feel super readable, but grouping it into an address expression (unfortunately not a trivial change as currently designed) might clarify this?
For the first three the offset is an immediate (value of Ou doesn't matter), and for the last three the offset is unsigned (uint u), and correctly marked as unsigned, or am I misunderstanding?
(@alyssarosenzweig Are you still interested in working on this, or should we just merge and others can PR fixes and improvements? It's already way better than nothing.)

A long shot, but maybe we can ask them if you need to test the output register.

You'd need to be able to write your own GPU code to get the output register, either by using Asahi's driver or through this repo's hwtest setup.  Metal wouldn't ever generate it, and it's probably useless since it's a 32-bit output from a 64-bit operation.  I was just kind of curious, that's all.

(@alyssarosenzweig Are you still interested in working on this, or should we just merge and others can PR fixes and improvements? It's already way better than nothing.)

I guess we can merge


Add log handler for custom handling

manage logs in multi-treads runs
#TODO

[ ] Xpress Interface/ tests
[ ] Sirius Interface/ tests
[ ] maybe update Sirius version

Possible improvements

Give EnableOutput an argument of type std::ofstream with default value std::cout
Let the caller (the application) determine where to write, i.e remove std::thread::get_id, etc.
Implement this logic for other solvers (COIN, etc.)

Maybe we need another flush method for interface LogHandlerInterface. The XPRESS doc indicates that nMsgLvl <0 indicates that it is necessary to synchronize logs, probably before a crash ?

that's a good point! We've outsourced message processing to the handler, so it's up to the caller to manage it.
changes are coming ....

Maybe we need another flush method for interface LogHandlerInterface. The XPRESS doc indicates that nMsgLvl <0 indicates that it is necessary to synchronize logs, probably before a crash ?

that's a good point! We've outsourced message processing to the handler, so it's up to the caller to manage it. changes are coming ....
i'm taking care of the default handler...


Allow q1simulator to be used as an InstrumentChannel

When using q1simulator in a simulator for the Cluster module, problems occur because then we have a qcodes.Instrument inside a qcodes.Instrument. Some parts of qcodes do not handle this well (Instrument.close_all).
With this PR a new class is introduced that can be used as an InstrumentChannel. I think this is a reasonably clean construct ...

I've added Cluster and ClusterModule to q1simulator.
ClusterModule is Q1Simulator dressed as an InstrumentChannel.
Actually, the functionality of Q1Simulator is moved to Q1Module.
Q1Simulator is subclass of qcodes.Instrument and Q1Module.
ClusterModule is a sublcass of qcodes.instrument.InstrumentChannel and Q1Module.
Cluster is a qcodes.Instrument and has ClusterModules as submodules.


Rows break Slide Syncing

I can get slide syncing to work fine with a single row, but as soon as I break it up into multiple rows, the syncing stops working.

Closing pending edit of this issue to conform to guidelines detailed in https://github.com/kenwheeler/slick/blob/master/CONTRIBUTING.markdown


allow_unknown inside *of rule is ignored

When trying to use allow_unknown within an *of clause, validation fails.
This is perhaps related to #250 , but as no exception is thrown in this case and the error tree is seemingly successfully built and only ignores the allow_unknown flag, I'm opening a separate issue.

# This is the schema that causes the problem
schema1 = {
    'test': {
        'oneof': [
            {
                'type': 'dict',
                'allow_unknown':True,
                'schema': {'a': {'type': 'string'}}
            }
        ]
    }
}

# This is a control schema, meaning it is the same as the above,
# just without wrapping the `oneof` clause around the inner `'dict'`
schema2 = {
    'test': {
        'type': 'dict',
        'allow_unknown':True,
        'schema': {'a': {'type': 'string'}}
    }
}

v1 = cerberus.Validator(schema1)
v1.validate({'test': {'a': 's'}}) #  returns True (as expected)
v1.validate({'test': {'a': 's', 'b': 'asd'}}) #  returns False (is `allow_unknown` ignored?)
print(v1.errors) #  {'test': [{'oneof': ['none or more than one rule validate', {'oneof definition 0': ['unknown field']}]}]}

v2 = cerberus.Validator(schema2)
v2.validate({'test': {'a': 's', 'b': 'asd'}}) #  returns True (as expected)

This has nothing to do with #250 as it turns out.


Remove haste imports from Slider

removed haste imports from Slider component

Nice! How about other imports like 'ImageSource'?

Flow types fixed :)


[BUG] Formulas are not calculated when import implements WithCalculatedFormulas with SkipsEmptyRows

Versions
Laravel version: 8.12
Php version: 8.0.3
Laravel-Excel version: 3.1.30
Description:
When the import class implements WithCalculatedFormulas and SkipsEmptyRows formulas calculation doesn't work. It seems like Row::isEmpty execution in ModelImporter::import (line 61) leads to this behavior. There's a condition:
if (!$import instanceof SkipsEmptyRows || ($import instanceof SkipsEmptyRows && !$row->isEmpty())) {

Outside of the condition, execution Row::toArray returns valid values. But inside formulas are not calculated. However, if the import class doesn't implement SkipsEmptyRows so the second part of the condition isn't executed, formulas are calculated as it supposed to be.
Expected behavior:
SkipsEmptyRows should not affect formulas calculation

Feel free to open a PR with a fix or if not sure, a failing unit test.

Closing as PR is merged


[bug] NPM releases are deprecated (apart from release candidate versions)

Describe the bug
SortableJS versions up to 1.12.0 have until recently been distributed via NPM.  Currently release versions of SortableJS on NPM are indicated as 'deprecated' and are unavailable for download.
To Reproduce
Steps to reproduce the behavior:

Go to https://www.npmjs.com/package/sortablejs
View the package version history
Observe that only releases containing -rc in the version tag (release candidates) are listed
To see the previously-available (now deprecated) versions, check the 'show deprecated versions' checkbox

Expected behavior
Previously-released versions of SortableJS should be available via NPM, or a descriptive reason explaining the deprecation of the package versions should be provided on the NPM package page and GitHub repository.

Yes, this was a mistake due to a problem with npm, I have contacted npm support to fix this and I'm waiting to hear back from them

No probs - thanks @owen-m1!

Fixed now

Thanks @owen-m1 - is there any background you can share on why the 1.12.0 release was deprecated?

@jayaddison It contained a lot of structural changes to the codebase that we deemed unnecessary, as well as some build issues. Since this was the majority of the updates it was just rolled back to an earlier version. Any bug fixes that there were in 1.12.0 I will merge into the current version and release as a new version.


Orphaned code on united_states.py, commit c4a2a0f

If I'm not mistaken, lines 378 through 381 are orphans.

Hey @Sudo-Rob that's correct! I applied your suggested fix and released in beta.
Thx, cheers!


Update manual matches (2022)

ORIS 2953 GEN_IDs 5A and 5B  were changed to the correct ORIS CODE 63628 so now they match exactly with CAPD
ORIS 56032 GEN ID 0001 was corrected in CAPD to match exactly with EIA

Hi Johnathan, thanks for your work on this. Is there a plan to update the crosswalk to use 2023 year data in the near future? We are currently attempting to use the crosswalk for publishing 2023 emissions data in our Open Grid Emissions dataset, but my understanding is that the currently published crosswalk still uses data from 2018 so is missing some associations.

Hi @grgmiller, you are correct in that the currently published crosswalk output uses 2018 data. We do have plans for a more extensive update for the crosswalk in the near future, but it is possible to run the crosswalk R script for the 2023 data year to produce an output for that year. I would just caution that we cannot guarantee the matches for that data year output as we have not QA'd it. Please do keep a lookout for updates in this repo as we undergo updates!


Contract creation transaction

This pr implements a contract creation transaction in addition to the logic needed in laserEVM to start executing a contract with creation code.
closes #191

In #404 @b-mueller mentioned the absence of different colours in the callgraph. They are back with this pr
Its now fix with the following addition
            if return_global_state is None:
                e.global_state.world_state.node = global_state.node <- this one
                self.open_states.append(e.global_state.world_state)
                new_global_states = []

When i ran this on https://etherscan.io/address/0xf6da07a8ffb5683314715d8c7a1a5c952b4e74ca#code by copy pasting it to a file, it threw an attribute error,can you check this?

@norhh Great catch. If the constructor "fails" then no contract is created. I didn't yet implement something that would handle that. Should be fixed now


[FLINK-11048] Ability to programmatically execute streaming pipeline with savepoint restore

What is the purpose of the change
Adds the ability to programmatically execute a job with savepoint restore option.
<EMAIL_ADDRESS>The number of parameters to executeRemotely is a bit higher than what we might have expected. The change to ScalaShellRemoteStreamEnvironment needs a closer look. It needs to override the jar file list, but do we really need the ProgramInvocationException there?
Brief change log

executeRemotely changed to static method that can be used with any StreamExecutionEnvironment

Verifying this change
No added test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@mxm I think the constructor proliferation suffers from its own issues: besides repetition you need to decide how to prioritize parameters that naturally have no priority. And again anything with a long parameter list is not only hard to read but also toxic for backward compatible code evolution.
Ideally we would just have one parameter to execute, which could be of type ExecutionParameters and hold the job name as well as the savepoint info. Anything else that might be needed in the future can be added without breaking the interface contract. But that isn't easy to accomplish due to how the code has been cast. The difficulty comes from the protected executeRemotely method that we cannot change. How about passing the savepoint parameter or before mentioned new parameters holder through a thread local instead of the instance variable? The difference how we pass it internally is cosmetic and not important to the user. The question of savepoint vs. generalized execution parameters seems more interesting.

I think the constructor proliferation suffers from its own issues: besides repetition you need to decide how to prioritize parameters that naturally have no priority.

That's the nature of fixed method parameters. I agree that "ExecutionParameters" would be nicer, essentially just a map of config parameters with no order imposed.

How about passing the savepoint parameter or before mentioned new parameters holder through a thread local instead of the instance variable? The difference how we pass it internally is cosmetic and not important to the user. The question of savepoint vs. generalized execution parameters seems more interesting.

I don't think that would change much. Granted, other threads wouldn't be able to see the savepoint options, but I think that would make the behavior even more unexpected.
Until this is refactored, IMHO it is ok to add another constructor parameter or another parameter to the execute method.

Just to sum up my review.

Personally would prefer method execute(String jobName, SavepointSettings savepointSettings, but I am ok with the ctor as well
Before merging this PR please annotate newly introduced methods/ctor with @Internal or at least @PublicEvolving

After that I am +1

Just to sum up my review.

Personally would prefer method execute(String jobName, SavepointSettings savepointSettings, but I am ok with the ctor as well
Before merging this PR please annotate newly introduced methods/ctor with @Internal or at least @PublicEvolving

After that I am +1

@dawidwys thanks for the review. I marked the new method public static JobExecutionResult executeRemotely as evolving. I would also prefer the execute method with the savepoint restore settings (the previous version of the PR had that actually). Unfortunately we had to discard that (in favor of the constructor) because it would require the savepoint restore parameter to be passed through a member variable to still be able to call protected JobExecutionResult executeRemotely(StreamGraph streamGraph, List<URL> jarFiles), which we have to for backward compatibility..

@mxm the contract requires us to call this method (we could also not modify the existing execute method to bypass it). Hence my earlier revision stored the savepoint settings in a member variable, which IMO would have been a reasonable compromise: https://github.com/apache/flink/pull/7249/commits/c10f8dfc390de2b24b5037daa8cef5749389106c

@mxm Let's leave it as is. The main point was addition of the static method, which effectively decouples StreamExecutionEnvironment from where the job is executed.

That was a tough one. Thanks for considering all of our comments!

Hi @tweise may I ask the original purpose we change here for executeRemotely? Is it still used in other projects?

@TisonKun this is for Beam or any other client that wants to programmatically start the job from savepoint (see JIRA). In Beam we are going to use this once we remove support for older Flink versions that don't have the feature.


Allow useBlockingTaskExecutor in Thrift services

Similar to how users can set useBlockingTaskExecutor on GrpcServiceBuilder and offload execution of the users' code into a "blocking task executor", let's introduce mirroring functionality for ThriftServiceBuilder.

I think it's interesting.
May I handle this?


Change to png asciinema preview

The SVG version locks up the tab for me in Firefox, and I am on a fairly beefy machine. The preview image is also very large, so downscaling it a bit may be preferrable for saving vertical space + help with sharpness on retina

For some reason the play button is cropped. That's weird. And if people don't understand that you need to click on it, I don't know if it is a good idea...

idk how to fix the play button, I think I'll just give up on this

Thanks anyway

Hey @untitaker mind having a re-look now?
I went down the rabbithole with #139

lgtm, thank you!

Tanks for your work, both of you


Pass through itemset ref case

Closes #642
Why is this the best possible solution? Were any other approaches considered?
I decided to go with an exclude list for case normalization when first parsing parameters. The alternative I considered was to move case normalization to when parameter values are used by pyxform. I don't feel strongly between the two. Currently label and value are the only parameters that get set to user-provided strings. All of the others are numeric or enum values.
I also considered making sure all clients use label and value case-insensitively and leaving pyxform as it is. Even if we do choose to go that route, I don't think pyxform should be responsible for case normalization.
What are the regression risks?
The only risk I can see would be if some client somewhere counts on label and value references always being lowercase. However, alternate clients are not common.
Does this change require updates to documentation? If so, please file an issue here and include the link below.
No.
Before submitting this PR, please make sure you have:

[x] included test cases for core behavior and edge cases in tests
[x] run nosetests and verified all tests pass
[x] run black pyxform tests to format code
[x] verified that any code or assets from external sources are properly credited in comments

@lindsay-stevens although this has been an issue for a while, now that we know about it I think it should be fixed as soon as we can. There's a Central release that's planned for next week and I'd love to include it.
Very interested in seeing what you think of the approach and whether you find it pragmatic or backwards.

Not sure I entirely understand the full context, but...

The only risk I can see would be if some client somewhere counts on label and value references always being lowercase.

In my client I'm certainly not making assumptions that select values are supposed to be case-insensitive (eg always lowercase).
FWIW I dont see any mention of case (in)sensitivity in the spec: https://www.w3.org/TR/2003/REC-xforms-20031014/slice8.html#ui-common-choices-value

select values

This is about the value and label references for defining itemsets. By default the value reference is name and the label reference is label. But those can be customized if e.g. you are using a file from another system that doesn't nave name and label elements/attributes/columns. In your XLSForm, you can specify something like value=XYZ_ID label=DisplayName. But currently the two values (XYZ_ID and DisplayName) are set to lowercase.
In an XML context it would be very unusual/go against the spec to treat element names as case-insensitive. I think it's would be a bit weird with CSV column names and geojson properties too though probably more common. Regardless, it's clear to me that pyxform should pass through the case provided by the user.

Regardless, it's clear to me that pyxform should pass through the case provided by the user.

+1


Add Pods cache dir to ios/.gitignore

Fixes https://github.com/flutter/flutter/issues/9085

Merging. The broken flutter-build appears to be a flake as it passed in a re-run.


Hong Kong Rainstorm Record Analysis

ML-Crate Repository (Proposing new issue)
:red_circle: Project Title : Hong Kong Rainstorm Record Analysis
:red_circle: Aim : Analyse the different aspects of rainstorm of Hong Kong.
:red_circle: Dataset : https://www.kaggle.com/datasets/henrychan1862/hong-kong-rainstorm-record-apr1998aug2022
:red_circle: Approach : Try to use 3-4 algorithms to implement the models and compare all the algorithms to find out the best fitted algorithm for the model by checking the accuracy scores. Also do not forget to do a exploratory data analysis before creating any model.

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be four main components.

Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.

Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.
This issue is only for 'SWOC' and 'JWOC' contributors of 'ML-Crate' project.

:white_check_mark: To be Mentioned while taking the issue :

Full name :
GitHub Profile Link :
Participant ID (If not, then put NA) :
Approach for this Project :
What is your participant role? (Mention the Open Source Program name. Eg. HRSoC, GSSoC, GSOC etc.)

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

i can solve this issue

Hello I would like to work on this project. Please assign it to me
Full name : Gunesh Mahajan
GitHub Profile Link : https://github.com/guneshm11
Participant ID (If not, then put NA) : NA
Approach for this Project : Try to use 3-4 algorithms to implement the models and compare all the algorithms to find out the best fitted algorithm for the model by checking the accuracy scores. Also do not forget to do a exploratory data analysis before creating any model.
What is your participant role? - Contributor

Issue assigned to you @guneshm11

Issue has been un-assigned from you due to inactivity.
@guneshm11

@abhisheks008  Is this a data analysis project?

Yup Data Analysis and Visualization.
@susanyeldo

Hello I would like to work on this project. Please assign it to me
Full name : Susanna Yeldo
GitHub Profile Link : https://github.com/susanyeldo
Participant ID (If not, then put NA) : NA
Approach for this Project : Try to use 3-4 algorithms to implement the models and compare all the algorithms to find out the best fitted algorithm for the model by checking the accuracy scores. Also do not forget to do a exploratory data analysis before creating any model.
What is your participant role? kWOC

Issue assigned to you @susanyeldo


Release 0.7.1 patch

We need #335 to land on crates. There may potentially be other things that could be included.
@MomoLangenstein or @torkleyy - would you be interested in driving the patch release?

@kvark I'd be very happy to work on the release. As I haven't created and uploaded a release before, I might need some brief guidance.
I think an updated version of #334 should also be included (otherwise we'd move the struct_names option to PrettyConfig just to move it again in the next update). Since there hasn't been any progress on that PR, I could take care of rebasing its changes on the current main branch and moving the option to Options.
#363 would be a very small change that could be included / closed as well.

Edit: I had another think about #334 and at least for me I'm still not sure what the correct way there is. To get 0.7.1 to land quickly, it might be easier to just skip it and potentially move the struct_names config later.
I think it is correct that struct_names does more than just make the RON prettier (but so does decimal_floats, just to a lesser extent). Moving it to Options, however, also doesn't feel quite right as it only affects the Serializer so far. We could introduce a similar option for the Deserializer to enforce including struct names if enabled. Another option would be to go with the _advanced function pattern, but add new extensible config structs (like PrettyConfig) for both the Serializer and Deserializer, to allow them to more easily evolve should more options be needed in the future.

Thank you for helping!
We'd need to summon @torkleyy about process here, since they convinced me to change the release/contribution workflow some time ago relative to what I do for all other projects, which resulted in #327 .
In other projects we'd just back-port some of the commits onto v0.7 branch and publish a patch from there.

Yes, that would work as well

Yeah, we'll be doing a version churn, causing downstream to diverge in the used RON versions and produce duplicates in the vendored trees. This is quite unfortunate. Are you sure the simplified workflow is worth it?

Well, I don't think many libraries should be using RON, so I don't expect RON to be deep in a dependency tree.

There is quite a few libraries - https://crates.io/crates/ron/reverse_dependencies
Notably: wgpu, naga, specs, egui, bevy stuff, amethyst stuff, etc

Alright, then how about we cherry-pick the necessary fixes onto a v0.7 branch, release 0.7.1 and release master as 0.8.0?

Why do we need to release master as 0.8 now? Is there any feature users need today that wouldn't be published in 0.7.1?

Fixed by #382