Q: ETA for a non-pre-release version?

Just a quick question, and since I haven't found a better place to ask (is there one?): are there plans already when the extension could move out of pre-release?
I have a VSCode extension here (https://marketplace.visualstudio.com/items?itemName=floooh.vscode-kcide) which is now pretty much ready to use. The extension runs a cmdline assembler tool via the WASI extension and it's working fine. The only downside is that users must install the extension as pre-release, otherwise installing the ms-vscode.wasm-wasi-core extension won't work.
Even though I mention that caveat promimently in the documentation, users are still likely to stumble over that problem since it differs from how VSCode extensions are usually installed.
IMHO, releasing a non-prerelease version of the WASI extension wouldn't be much of a problem if the major version number stays at 0, and the extension is marked as "Preview" in the marketplace?

I will look into this this month and decide if we can make a release version of the extension and what the consequences are. Moving the WASM support into VS Code core will very likely not happen. VS Code core is actually already "big" and moving more code into it only makes development on the core more complicated.
See https://github.com/microsoft/vscode-eslint/issues/1842#issuecomment-2095506576 for why we are currently not publishing to Open-VSX and what the options are.

We decided to provide a release version of the extension and the wasm-wasi API npm module.
To allow further improvements to the API the npm module wasm-wasi will provide different routes to import different API versions. The API provided by the default import import { Wasm } from '@vscode/wasm-wasi'  is deprecated together with all other types from that route. The npm module exports new routes to be able to serve different API versions. The current route for the API (which is the same as before) is import { Wasm } from '@vscode/wasm-wasi/v1' There might be new routes in the future to cover a v2 version of the API or a proposed route to test proposed API.
The v1 import works with the current pre-release version of the WASM WASI Core extension (e.g. 0.13.3) and will work with the upcoming release version of the WASM WASI Core extension (e.g. 1.0.0)

Thank you!

To be prepared for the release of the WASM WASI Core extension exiting extensions that have a dependency onto the WASM WASI Core extension should move to<EMAIL_ADDRESS>version of the npm module.

OMG it's happening!

Now I'm eagerly waiting for this to happen 👀

Will close the issue.


Polling empty responses?

https://github.com/vivek12345/react-polling/blob/6a807c2b535aace01b342c7ee627c8f61d970c4e/src/ReactPolling.js#L127
I'm attempting to use the component for an asynchronous REST service, where the /status endpoint will respond with 202 and an empty response body until the service eventually succeeds.
However, since the response function evaluates Body.json(), I'm suspecting the polling stops on an unhandled error.  Perhaps the function should guard with a test for non-empty body before evaluating Body.json()?

I am also facing this issue, I am receiving plain text response from an API successfully, but the library is considering it as failure. It triggers onFailure after receiving the success response 200.

Hey @asgeirn and @qtcoder999 , apologies for the delay. The last couple of months have been really hectic in terms of work.
But I am hoping latest release v1.0.7 will address all your concerns.
Thank you for creating this issue and I hope the new release is helpful.
Please try it and let me know if it fixes your issue.

Hi,
I've just tested v1.0.8, but unfortunately this didn't work for our case.  We've worked around it with a fork where we've added the following :
          if (resp.headers.get('Content-Length') === '0') {
            if (resp.ok) {
              return resp;
            } else {
              return Promise.reject({ status: resp.status, resp });
            }
          }


List of memory-managed objects

Currently, creating a list of memory-managed objects like Numpy arrays in nopython mode throws this error: unsupported nested memory-managed object.
How difficult is it to support this?

For anyone looking, lists of nested memory-managed objects would include things like:

list of lists
list of sets
list of NumPy arrays (and extensions of/arrays like)

Is extending this issue's scope to include nested memory-managed objects in general, such as set[list], set[set], list[set[set]], etc. better or would opening a separate issue be more appropriate?

looking forward to this feature being implemented in numba 0.38.  It is cumbersome to write linked list of jitclass.

Hello. Is this feature likely to make it into Numba 0.39? And will it have nested memory managed objects, or just lists?
I ask because it's a blocker for quite some things in pydata/sparse.

I, too, have encountered several instances where not having this (even just a single-deep list of numpy arrays) makes me have to jump through hoops and write ugly code to get something to work (if at all). This feature would be a huge boon to my using Numba (and this greatly broadens the scope of the kinds of problems that can be solved with Numba).

Is extending this issue's scope to include nested memory-managed objects in general, such as set[list], set[set], list[set[set]], etc. better or would opening a separate issue be more appropriate?

These aren't valid in Python -- do you mean set[tuple], set[frozenset], list[set[frozenset]], etc?

Closing, this was added in https://github.com/numba/numba/pull/2840 and is in the 0.39.0 release.


[Bug] Periodically getting macro initialization error for incremental models within ClickHouse

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
Currently when the last dbt model in a long chain of dbt is models is running, it will sometimes produce an error that reads as so:
Compilation Error in model dex (models/dex.sql) 19:26:52    __init__() missing 1 required positional argument: 'msg' 19:26:52     19:26:52    > in macro materialization_incremental_clickhouse (macros/materializations/incremental.sql) 19:26:52    > called by model dex (models/dex.sql) 19:26:52   19:26:52  Done. PASS=241 WARN=0 ERROR=1 SKIP=0 TOTAL=242
What is weird is that those models do not use any macros explicitly, they just combine the output from several different feeder tables into one unified schema. The error comes in periodically and will often go away on its own and come back again, with little consistency.
Expected Behavior
Since the model uses no macros, I would expect it to run without a macro error.
Steps To Reproduce
Cannot currently reproduce because the error happens randomly on a full dbt run that takes place 144 times a day, about 20 times in a day this error tends to show up in one of two final dbt models.
Relevant log output
No response
Environment
- OS: macos-12
- Python:
- dbt: 1.4.5

Which database adapter are you using with dbt?
other (mention it in "Additional Context")
Additional Context
We run on a Clickhouse database adapters.

Thanks for reaching out @gurjotd23.
Can you check your logs/dbt.log file to see if there is more detail (like a Python stacktrace)?
Based on what you shared it looks like something is periodically going wrong within the Clickhouse incremental materialization (which dbt compiles to a macro named materialization_incremental_clickhouse).
Depending on what you find in the logs, we may ask you to re-open this issue within dbt-clickhouse instead.

Hello @dbeatty10 thank you very much for responding. This might be a noob question but would you know how I can get the logs for the runs that take place on the github actions? Currently there is a logs folder and file but no logs to speak of. I can only think of maybe exporting workflow artifacts using this, but not sure it will support clickhouse: https://hub.getdbt.com/brooklyn-data/dbt_artifacts/latest/

would you know how I can get the logs for the runs that take place on the github actions? Currently there is a logs folder and file but no logs to speak of.

I don't know, sorry. But we'll definitely need to examine those to know how to proceed, so good luck! 🙏


logical indices on RLEVector{String} failed with UndefRefError

I got the following error when using logical indices on a RLEVector{String}
julia> a = RLEVectors.RLEVector(["aa", "bb", "cc"])

julia> a[[true, false, true]]
ERROR: UndefRefError: access to undefined reference
Stacktrace:
 [1] getindex at ./array.jl:809 [inlined]
 [2] setindex!(::RLEVectors.RLEVector{String,Int64}, ::String, ::Int64) at /Users/x/.julia/packages/RLEVectors/ZW6hy/src/indexing.jl:74
 [3] macro expansion at ./multidimensional.jl:772 [inlined]
 [4] macro expansion at ./cartesian.jl:64 [inlined]
 [5] macro expansion at ./multidimensional.jl:767 [inlined]
 [6] _unsafe_getindex! at ./multidimensional.jl:762 [inlined]
 [7] _unsafe_getindex(::IndexLinear, ::RLEVectors.RLEVector{String,Int64}, ::Base.LogicalIndex{Int64,Array{Bool,1}}) at ./multidimensional.jl:757
 [8] _getindex at ./multidimensional.jl:743 [inlined]
 [9] getindex(::RLEVectors.RLEVector{String,Int64}, ::Array{Bool,1}) at ./abstractarray.jl:1060
 [10] top-level scope at REPL[8]:1

Interestingly, logical indices on RLEVector{Int64} or any other type works
julia> b = RLEVectors.RLEVector([1,2,3])

julia> b[[true, false, true]]
RLEVectors.RLEVector{Int64,Int64}
 Run values: [1, 3]
 Run ends: [1, 2]

I guess this is due to the fact that similar(a) creates undefined reference. For example:
julia> similar(a)
RLEVectors.RLEVector{String,Int64}
 Run values: [#undef]
 Run ends: [3]

julia> similar(a).runvalues[1]
ERROR: UndefRefError: access to undefined reference
Stacktrace:
 [1] getindex(::Array{String,1}, ::Int64) at ./array.jl:809
 [2] top-level scope at REPL[40]:1

Thank you for this report. I remember being unsure what to do with empty RLEVectors. runends has to be of length one to hold the length of the uncompressed vector. So, runvalues has to be of length one. I didn't want to want to make runvalues a Union of Missing and the target type (e.g. String), hence the undef. I thought this was a behavior similar to normal Vectors. I'll have another look.

@phaverty I guess it's fine to use undef and as you said this is similar to normal vectors. I looked into this a little bit and found that my issue may be fixed with the following patch, where isassigned is used to check whether one element of the array is undef
diff --git a/src/indexing.jl b/src/indexing.jl
index 3c9c26e..1103e61 100644
--- a/src/indexing.jl
+++ b/src/indexing.jl
@@ -71,6 +71,9 @@ end

 function Base.setindex!(rle::RLEVector, value, i::Integer)
     run = ind2run(rle, i)
+    if ! isassigned(rle.runvalues, run)
+        rle.runvalues[run] = value # substitute undef with valid value from user
+    end
     runvalue = rle.runvalues[run]
     runend = rle.runends[run]
     #value == runvalue && return rle # replace with same value, no-op

See if you like this solution.

OK, I see how this happens now. getindex with logical indices calls some of the AbstractVector code which makes an empty RLEVector and fills it one element at a time. The setindex! method for RLEVector fails when trying to compare the incoming value with the existing value (which is undef). The underlying problem is that I need a specialized getindex for RLEVector when the indices are Vector{Bool}. I'll add that.

@phaverty  I think it still worth fixing setindex! to account of undef (checking with isassigned). Things like broadcast, copyto! would rely on that. For example:
julia> rle = RLEVector(["aa", "bb", "bb"])

julia> rle .* "suffix"
ERROR: UndefRefError: access to undefined reference

and
julia> copyto!(similar(rle), collect(rle))
ERROR: UndefRefError: access to undefined reference

Yes, it is probably still worth doing. I'll either add the isassigned
into setindex! or come up with a special way of filling an empty
RLEVector.
On Thu, Dec 31, 2020 at 12:04 PM Marlin<EMAIL_ADDRESS>wrote:

@phaverty https://github.com/phaverty I think it still worth fixing
setindex! to account of undef (checking with isassigned). Things like
broadcast, copyto! would rely on that. For example:
julia> rle = RLEVector(["aa", "bb", "bb"])
julia> rle .* "suffix"
ERROR: UndefRefError: access to undefined reference
and
julia> copyto!(similar(rle), collect(rle))
ERROR: UndefRefError: access to undefined reference
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/phaverty/RLEVectors.jl/issues/44#issuecomment-753071882,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB6TMK7C2M3F4D7M3PL33I3SXTKNHANCNFSM4URMN65A
.

I'm sure there is a lot that could be done to optimize the broadcast stuff,
so I'll be looking at that specifically. Right now I just fall back to the
default stuff which iterates over the whole array. It should be possible to
have broadcast be more like map where scalars just get applied to each
runvalue once.
On Thu, Dec 31, 2020 at 1:16 PM Peter Haverty <
<EMAIL_ADDRESS>wrote:

Yes, it is probably still worth doing. I'll either add the isassigned
into setindex! or come up with a special way of filling an empty
RLEVector.
On Thu, Dec 31, 2020 at 12:04 PM Marlin<EMAIL_ADDRESS>wrote:

@phaverty https://github.com/phaverty I think it still worth fixing
setindex! to account of undef (checking with isassigned). Things like
broadcast, copyto! would rely on that. For example:
julia> rle = RLEVector(["aa", "bb", "bb"])
julia> rle .* "suffix"
ERROR: UndefRefError: access to undefined reference
and
julia> copyto!(similar(rle), collect(rle))
ERROR: UndefRefError: access to undefined reference
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/phaverty/RLEVectors.jl/issues/44#issuecomment-753071882,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB6TMK7C2M3F4D7M3PL33I3SXTKNHANCNFSM4URMN65A
.


TripDescriptor hasScheduleRelationship incorrectly returns false

When working with the SEPTA GTFS-Rt feed, I found that the TripDescriptor hasScheduleRelationship() was returning false even for times when there were SCHEDULED schedule relationships present. SEPTA does not have any other statuses in their feed besides SCHEDULED, so that is all I was able to test. I'm unsure if this issue is present for other statuses.

@zachpepsin Do you have a snippet of the feed in plain text you can share?
Off the top of my head I'm pretty sure this is one of the quirks of protocol buffers and the Java implementation, although from Googling now I can't find an explicit reference that says this. Because SCHEDULED is the default enum value for TripDescriptor, the bindings may just ignore it.
If you get the value, though, it should still return SCHEDULED, even if the SCHEDULED value doesn't appear in the message itself.

@barbeau I pasted below a TripDescriptor object that I just pulled from SEPTA's feed.  You can also see that hasScheduleRelationship() returns false while the property returns SCHEDULED.  You may be right that a TripDescriptor wasn't provided, so it defaulted to SCHEDULED. yet the hasScheduleRelationship() still remains false.

Looking at http://www3.septa.org/gtfsrt/septarail-pa-us/Trip/rtTripUpdates.pb, here's a plain text version of a TripUpdate:
    {
      "id": "CHE_2720_V5_M",
      "trip_update": {
        "trip": {
          "trip_id": "CHE_2720_V5_M"
        },
        "stop_time_update": [
          {
            "stop_sequence": 35,
            "arrival": {
              "delay": 120,
              "uncertainty": 300
            },
            "stop_id": "90406"
          }
        ],
        "timestamp":<PHONE_NUMBER>
      }
    },

So yes, it looks like they aren't populating the schedule_relationship field in the protocol buffer message.
So this is behaving as expected for protocol buffer bindings - hasScheduleRelationship() returns false because the original message didn't contain the field, but if you get the schedule relationship from the object it will still return the default value of SCHEDULED, because the default value if the field isn't populated is SCHEDULED.
This is just how Google's protocol buffer compiler works - you can read more about enumerations in protocol buffers here:
https://developers.google.com/protocol-buffers/docs/proto#enum

Thans @barbeau!  Is this something you think is worth mentioning to SEPTA or do you think it's fine for them to not set the ScheduleRelationship and assume the default enum?

@zachpepsin My personal opinion is that explicitly specifying the field is better than leaving it empty and having consumers assume the default. But if they are going to put energy into updating their feed my guess is that there are probably higher priority items they could be tackling.


NetworkBehaviour validation error on child (Nested) Prefabs

Describe the bug
Error message will appear for any child (Nested) Prefab of Player Prefab used in NetworkManager as Player Object that contains NetworkBehaviours:
"NetworkBehaviour" on NetworkBehaviourPrefab requires a NetworkIdentity. Please add a NetworkIdentity component to NetworkBehaviourPrefab or it's parents.
[IMPORTANT] How can we reproduce the issue, step by step:
Please tell us how to reproduce your issue, STEP BY STEP, with one of our built in examples:

Open any example scene with NetworkManager
Create gameobject "PlayerRoot"
Add NetworIdentity to PlayerRoot
Create gameobject "PlayerChild" in "PlayerRoot"
Add NetworkTransform(Unreliable) to "PlayerChild"
Drag "PlayerChild" to assets (create prefab from it) - there will be error(s) in log
Clear errors
Drag "PlayerRoot" to assets (create prefab from it)
Delete "PlayerRoot" from Scene
Open "PlayerChild" - there will be error(s) in log again
Close "PlayerChild" and return to scene, Clear errors.
Use "PlayerRoot" as NetworkManager PlayerPrefab, error can appear again
Run scene, there will be error again

optional 14) If scene is saved after all these steps and then UnityEditor closed and restarted it could be that error won't appear on running scene.
optional 15) But if you open "PlayerChild" prefab again then there will be error on every scene start until UnityEditor restart.
Expected behavior
No error message
Screenshots

Desktop (please complete the following information):

OS: Windows
Build target: Windows(mono)
Unity version: 2021.3.25f1, 2022.3.0f1, 2022.3.3f1
Mirror branch: master, release v81.1.0

Additional context
Related to Issue #3550 and Pull request #3551

this was recently fixed. if not, let us know!

@vis2k Latest version still gives error.

@vis2k This is a different issue than #3550
#3550 was fixed, and this is not.
One of possible solutions for eliminating errors this issue is #3555


Cache custom types OIDs on Postgres

Resolves #2071
This avoids sending one query per custom type bind, which caused a lot of back and forth to the database when inserting a large numbers of lines that used a custom type.
Note: The implementation was also discussed on the issue (#2071).

Test fails are due to rand being down. x)
https://github.com/rust-random/rand/issues/818

I just made azure and travis re-run.


Migrate the app to Material 3

Update Flutter SDK

Run flutter upgrade in your terminal or command prompt.

Update dependencies

Update your pubspec.yaml file to use the latest version of the material-components-flutter package or the flutter package that supports Material You.

ThemeData changes

Update your ThemeData to incorporate Material 3-specific properties.

Replace deprecated widgets

Replace FlatButton with TextButton, RaisedButton with ElevatedButton, and OutlineButton with OutlinedButton.

Implement new components

Use new Material 3 components such as the NavigationRail, TimePicker, and RangeSlider.

Use updated typography

Replace the textTheme property with TextTheme using the updated text styles.

Adaptive design

Ensure your app uses adaptive widgets and layouts.

Customize color schemes

Update your app's color scheme using the new ColorScheme properties.

Test and iterate

Thoroughly test your updated app on different devices and platforms.

Update documentation

Update any documentation or design guidelines specific to your app.

Migrate the app to material UI 3 to close this issue.

assign this issue to me

@fredfalcon  @just-ary27 can I work on this issue ?

yes, you don't have to ask you can self assign, thank you

Yes, I knew it, just double-checking.

/assign

/assign

@just-ary27 How do you think I should approach this ?


Airflow APIs coverage

Describe your changes :

I worked on the ..... because ...

Type of change :

[x] Bug fix
[x] Improvement
[x] New feature
[] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[] Documentation

Frontend Preview (Screenshots) :
For frontend related change, please link screenshots of your changes preview! Optional for backend related changes.

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers

We have to update also this line to:
        sed -i 's/openmetadata_managed_apis/\/github\/workspace\/openmetadata-airflow-apis\/openmetadata_managed_apis/g' openmetadata-airflow-apis/ci-coverage.xml

We forgot to add this @pmbrull


[ISSUE #5965] Fix lmqTopicQueueTable initialization

Make sure set the target branch to develop
What is the purpose of the change
Fix lmqTopicQueueTable initialization
Brief changelog
XX
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage: 52.255% (+0.05%) from 52.207% when pulling 2d351c8ce03956526bfc7c8227a45dc6541bb517 on pingww:4.9.x into e5637e2c1eb4d7e27fa6fb5d6e02f9eae5569d92 on apache:4.9.x.


config(tiflow): remove required status check of leak-test in part of branches

ref task-3 in https://github.com/pingcap/tiflow/issues/6094
jenkins-ticdc/verify has covered all tests included in idc-jenkins-ci/leak-test and idc-jenkins-ci-ticdc/unit-test
Besides I can't find the test entrance of idc-jenkins-ci/leak-test, maybe there are configured in Jenkins backend.
jenkins-ticdc/verify is added since release-5.4, we can remove idc-jenkins-ci/leak-test from release-5.4

PTAL @wuhuizuo

/cc @hi-rustin

/ok-to-test

/merge

🥳 🥳 🥳


Initialize variables properly for b2RopeTuning

stretchHertz and stretchDamping were not initialized for b2RopeTuning and these can cause floating point exceptions on embedded systems if they for example result in unimplemented operations such as multiplication by denormalized floats. I'm not sure on the actual values and I can open an issue if necessary.

69276dc33204891b9c3f51d4352a684a041e25c4


Test Consider API for changing tree view title dynamically

refs: https://github.com/microsoft/vscode/issues/80208

[x] anyOS @isidorn
[x] Windows @dbaeumer

Complexity: 3
Test the proposed title TreeView API:
	export interface TreeView<T> {
		/**
		 * The name of the tree view. It is set from the extension package.json and can be changed later.
		 */
		title?: string;
	}

The tree view sample extension is a good place to start: https://github.com/microsoft/vscode-extension-samples/blob/master/tree-view-sample/src/testView.ts#L6

Verify that the inline documentation makes sense.
Verify that the title of the tree view is correctly sourced from the package.json first
Verify that you can get the title as set in the package.json even if you never set it.
Test that you can always get the title.
Test that you can change the title

Works nicely, nice job! I have tested on the macOS.


all: Replace moved links with their new locations

isn't this docs instead of all?

A bit of both, I guess. I was thinking of docs as README.md, ARCHITECTURE.md, and misc developer documentation, but I think docs makes sense for this too. Will switch. :P


Skip duplicated sections

Occasionally, there are duplicated sections in the data stack. They do not provide any additional valuable information for subsequent steps of the reconstruction pipeline. The feature should give a way of skipping those sections from aligning procedure.

How should be decided which sections to skip? Should we add another parameter which is a list of section-IDs that should be skipped? That would probably be the easiest from a development point of view. However, is it possible to know beforehand which sections need to be skipped?

I think list of section-IDs to be skipped would already helpful. A major cause of section duplicates is that the block-face was not cut and the same section was imaged twice or more times. This kind of duplicates are noted manually by the microscope user during acquisition, and can therefore be known beforehand.
Other cases I am not sure, @TomasGancarcik  may have better ideas.

In the first step, the list of sections to be skipped will be known beforehand. It can be simple text file with IDs of duplicates, or some other user editable file(s) within the SBEM project(s). In the future, we would like to run the alignment routine while the image acquisition is running and therefore a modified approach will be used.

Feature implemented in the new workflow:

Set section parameter 'skip' to True.
Commit changes
Run flow


[Documentation] Readme update

Your idea:
I installed the local version of HB, and had a hard time doing so, even following the set of steps on the readme, for that reason i'm going to review those steps, see where programs have changed, and add beter explanations when i can, this is related to the issue #1896.
Anyone who wants to help is invited to do so.

Right now the readme instructions look as follows:
Quick Start
The easiest way to get started using The Homebrewery is to use it on our website. The code is open source, so feel free to clone it and tinker with it. If you want to make changes to the code, you can run your own local version for testing by following the installation instructions below.
Installation
First, install three programs that The Homebrewery requires to run and retrieve updates:

install node

install mongodb (Community version)
For the easiest installation, follow these steps:
i. In the installer, uncheck the option to run as a service.
ii. You can install MongoDB Compass if you want a GUI to view your database documents.
iii. Go to the C:\ drive and create a folder called "data".
iv. Inside the "data" folder, create a new folder called "db".
v. Open a command prompt or other terminal and navigate to your MongoDB install folder (C:\Program Files\Mongo\Server\4.4\bin).
vi. In the command prompt, run "mongod", which will start up your local database server.
vii. While MongoD is running, open a second command prompt and navigate to the MongoDB install folder.
viii. In the second command prompt, run "mongo", which allows you to edit the database.
ix. Type use homebrewery to create The Homebrewery database. You should see switched to db homebrewery.
x. Type db.brews.insert({"title":"test"}) to create a blank document. You should see WriteResult({ "nInserted" : 1 }).
xi. Search in Windows for "Advanced system settings" and open it.
xii. Click "Environment variables", find the "path" variable, and double-click to open it.
xiii. Click "New" and paste in the path to the MongoDB "bin" folder.
xiv. Click "OK" three times to close all the windows.

install git (select the option that allows Git to run from the command prompt).

Checkout the repo (documentation):
git clone https://github.com/naturalcrit/homebrewery.git

Second, you will need to add the environment variable NODE_ENV=local to allow the project to run locally.
You can set this temporarily in your shell of choice:

Windows Powershell: $env:NODE_ENV="local"
Windows CMD: set NODE_ENV=local
Linux / macOS: export NODE_ENV=local

Third, you will need to install the Node dependencies, compile the app, and run it using the two commands:

npm install
npm start

You should now be able to go to http://localhost:8000/ in your browser and use The Homebrewery offline.

For starters, i ran into more than 5 different errors just by configurating mongodb, so i'll list a few resources that were useful, even though they may be old:

Course on cluster administration, in the mongodb web, useful for begginners
Mongo community forums
After mongodb 6.0, which i reccomend, to run mongo commands, users will have to install MongoDB Shell from this link.
Useful Stack Overflow links for your most probable errors: 1 2 3
These last links should not be included, as users should not run into these errors, but chances are that as mongo updates, this errors will appear again, by other causes but with simmilar solutions.

Then, in order to fix these errors one of the things i had to do was to move steps xi to xiv before step viii
There is also not explained how to set Node_env=local permanently, which i think should be.

With those fixes:
Quick Start
The easiest way to get started using The Homebrewery is to use it
on our website. The code is open source, so feel free to
clone it and tinker with it. If you want to make changes to the code, you can run
your own local version for testing by following the installation instructions
below.
Installation
First, install three programs that The Homebrewery requires to run and retrieve
updates:

install node, any version is supported.

install mongodb (Community version)
For the easiest installation, follow these steps:

In the installer, uncheck the option to run as a service.
You can install MongoDB Compass if you want a GUI to view your database documents.
If you install any version over 6.0, you will have to install MongoDB Shell.
Go to the C:\ drive and create a folder called "data".
Inside the "data" folder, create a new folder called "db".
Open a command prompt or other terminal and navigate to your MongoDB install folder (C:\Program Files\Mongo\Server\6.0\bin).
In the command prompt, run "mongod", which will start up your local database server.
While MongoD is running, open a second command prompt and navigate to the MongoDB install folder.
Search in Windows for "Advanced system settings" and open it.
Click "Environment variables", find the "path" variable, and double-click to open it.
Click "New" and paste in the path to the MongoDB "bin" folder.
Click "OK" three times to close all the windows.
In the second command prompt, run "mongo", which allows you to edit the database.
Type use homebrewery to create The Homebrewery database. You should see switched to db homebrewery.
Type db.brews.insert({"title":"test"}) to create a blank document. You should see WriteResult({ "nInserted" : 1 }).

install git (select the option that allows Git to run from the command prompt).

Checkout the repo (documentation):
git clone https://github.com/naturalcrit/homebrewery.git

Second, you will need to add the environment variable NODE_ENV=local to allow
the project to run locally.
You can set this temporarily in your shell of choice:

Windows Powershell: $env:NODE_ENV="local"
Windows CMD: set NODE_ENV=local
Linux / macOS: export NODE_ENV=local

If you want to add this variable permanently the steps are as follows:
1. Search in Windows for "Advanced system settings" and open it.
1. Click "Environment variables".
1. In System Variables, click "New"
1. Click "New" and write NODE_ENV as a name and local as the value.
1. Click "OK" three times to close all the windows.
This can be undone at any time if needed.
Third, you will need to install the Node dependencies, compile the app, and run
it using the two commands:

npm install
npm start

You should now be able to go to http://localhost:8000
in your browser and use The Homebrewery offline.
If you had any issue at all, here are some links that may be useful:

Course on cluster administration, in the mongodb web, useful for begginners
Mongo community forums
After mongodb 6.0, which i reccomend, to run mongo commands, users will have to install MongoDB Shell from this link.
Useful Stack Overflow links for your most probable errors: 1 2 3

If you still have problems, post in Our Subreddit and we will help you.

While it would add an extra application to the process, using Chocolatey could potentially greatly reduce the difficulty of installing Homebrewery on a Windows machine - potentially making it as simple and scriptable as Ubuntu/Debian.

While it would add an extra application to the process, using Chocolatey could potentially greatly reduce the difficulty of installing Homebrewery on a Windows machine - potentially making it as simple and scriptable as Ubuntu/Debian.

I ended up using docker and made the process way easier.


Project owner (and possibly other non-admins) cannot add members to a project

Spun out from https://github.com/rancher/dashboard/issues/4334, as we wait for monitoring to be accessible via projects, we should confirm that projects can have members added by non-admins.
@metal3d can you provide reproduction steps for us to verify?

Requires SURE-6164


Unable to set thread-names to identify threads inside of the gax thread pools

In debugging thread issues with Google Pub/Sub, I was frustrated by the Thread-2, Thread-3, ... names of threads originating from the Pub/Sub API code.  All thread pools should have the option of naming their threads for this reason.
Fixed by #536

@andreamlin can you add a priority to this?

Sounds like this is fixed by your PR https://github.com/googleapis/gax-java/pull/536 :)
so I'll close it out.


[BUG] tiles are still rendered as whitespace when the content length < pageSize

Describe the bug
When I use eg. :pageSize="40" and I scroll all the way to the bottom, the final section of the virtual grid will render tile placeholders for content that doesn't exist.
Since a single tile is about 1/3 of the screen height for me, it can render an immense amount of whitespace at the bottom.
Here is the DOM what the placeholder DOM element looks like:

You see that the previous one DOM element is the last one I have with content.
Expected behavior
The bottom tiles should not be rendered as whitespace when not provided by pageProvider. (Eg. the page provider returns only 1 result, and pageSize is 40, then ideally we only render 1 grid row or even better, 1 grid tile.)

Thanks for the bug report! It's been fixed in v1.2.2.

@rocwang Thank you so much!
I'm using 2.0.0-alpha.1, any chance you can fix it on that branch as well? : )
No rush though! thanks so much for all your work!
PS: Sorry I should've mentioned the version I was using!!

I'm using 2.0.0-alpha.1, any chance you can fix it on that branch as well? : )

@mesqueeb I don't I never released a 2.0.0-alpha.1 version on npm or have such branch on Github.
Did you mean some other library you use?

@rocwang Oh... I was looking at the wrong package!! Sorry 😅  ( I'm so used to looking at @next branches for Vue 3 :P )
Something seems to have gone wrong in the latest version, maybe just for us?
Once I installed it the grid won't render and there's this error:

Sorry, the screenshot didn't help much. I couldn't replicate the issue.
It looks like this issue. Maybe try reinstall the package?
If it still doesn't work for you, would you mind rend over a reproducible example? (e.g. a git repo)

@rocwang
hmmm, it's very weird, I tried reinstalling everything but can't even build my project now, I get this error : P

I will try to create a public reproduction

@rocwang I'm still trying to determine the cause, but cannot find it yet...
The latest version just won't work, but the one before that does.
Could it have something to do with rendering the grid while it's being hidden because some parent element is set to display: 'none' (v-show) ?

@rocwang Oh... I was looking at the wrong package!! Sorry 😅 ( I'm so used to looking at @next branches for Vue 3 :P )
Something seems to have gone wrong in the latest version, maybe just for us?
Once I installed it the grid won't render and there's this error:

Although https://github.com/rocwang/vue-virtual-scroll-grid/releases/tag/v1.2.3 adressed #154 instead of your error above directly, give it a try it maybe?

@rocwang I have just tested on 1.2.3, same issue.
I have just emailed your our repo with steps for you to open it on your end.
If you have some time we would greatly appreciate it.

Thanks for sending over the example over email.
I managed to get it to work by fixing the version of vue in the project to 3.2.22 as<EMAIL_ADDRESS>was built and tested against<EMAIL_ADDRESS>It looks like it has something to do with multiple versions of vue packages sitting under the same project, but I'm pretty sure vue-virtual-scroll-grid doesn't  include vue in the package.
Another change I made was removing the peerDependencies of vue from your db package as I didn't see it's used there.
While my fix works, it looks like your project use Quasar, which has its own dependant vue version. So I think the best solution might be upgrading Quasar to some version that depends on vue 3.2.22+. Don't take my fix as the final solution.
See:

https://github.com/vuejs/vue-next/issues/4344
https://github.com/vuejs/vue-next/issues/4478

A fixing patch is emailed to you.

@rocwang hey Roc!
Thank you very much for resolving my issue with the dependencies.
I just tried the latest version, but still found some issues.
Eg. When the pageSize is 40 and the array I put in is about 69 long, I still see about 11 tiles that should not render but are being rendered.

On mobile view for us it has 3 tiles per row, and therefore will take up many many times the screen height.
Can you look into the issue again? Let me know if you need anything from me.
Thank you very much.

@mesqueeb
I try to replicate the issue with your parameters (pageSize = 40, length = 69) under<EMAIL_ADDRESS>using this minimal repo: https://github.com/rocwang/vvsg-issue-152. However, it looks OK to me there and no item would be rendered beyond the 69th item.
Could you have a play there and see if you can see the issue. Or consider double checking the installed version of vur-virtual-scroll-grid, as the symptom was found in v1.2.1 indeed.

@mesqueeb
I had another play.
I see, it looks like the bug happens when the viewport is resized. Will look into that.

@rocwang thank you very much. I will send you another reproduction later today. Thank you for your patience.

@mesqueeb I wonder if this is still an issue to you?

@rocwang i'll check and let you know soon!!

Given the inactivity of this ticket, I'm going to close it.
Feel free to reopen it if needed.


Move default pagination to 20, 50, 100, all

Currently, the default pagination use Filament default configuration. I purpose to change this
It is more ergonomic and useful, show the products and items in a trice

This does raise the question as to whether we should have "all" as a default option.
Some tables will have thousands of records and so "all" is likely to be quite dangerous.

This does raise the question as to whether we should have "all" as a default option.
Some tables will have thousands of records and so "all" is likely to be quite dangerous.

I usually remove it from my Filament tables for that reason, so +1 from me.

There's an open Filament issue re: large table performance: https://github.com/filamentphp/filament/issues/9304. The consensus there was 100 max as well.
@glennjacobs I remember you saying something about wrangling with Livewire performance when creating Lunar’s datatables package. Maybe you've got some insights you could in the Filament issue to help the team improve this?

There's an open Filament issue re: large table performance: https://github.com/filamentphp/filament/issues/9304. The consensus there was 100 max as well.
@glennjacobs I remember you saying something about wrangling with Livewire performance when creating Lunar’s current datatables package. Maybe you've got some insights you could share in the Filament issue to help the team improve this?

The performance there was mainly Eloquent related which Filament v3 seems to have addressed pretty well. I agree, 100 max.

can this be configurable or use extension

@wychoong Exactly, i can create config/panel.php with configuration variables of panel and move pagination default.
@alecritson Do you have planned separate issue with global configuration of panel ?

I'm not keen on the config approach initially.
Having looked at Filament there doesn't appear to be a way to set the options globally.
I do wonder if Filament would consider a PR to allow pagination values to be set globally on the panel or something. I'd need to look at how doable that would be. Then it would be easy for a developer to change.

You mean setting global pagination settings like this?

You mean setting global pagination settings like this?

Ahha! I was searching for that and couldn't find it... that's exactly it.
So we could look to use that in our service provider, as long as devs can override it in their app service provider.

Nice thanks @sandervankasteel

Vous voulez dire définir des paramètres de pagination globale comme celui-ci  ?

We have two solutions to implement the global settings table configuration :
First :  we create a new options on LunarPanel Facade
      LunarPanel::configureTable(fn(Table $table) : void {
           // ...
        });

Second : Add on LunarPanelManger
        /*
        *   Default global settings for Page
        */
        Table::configureUsing(function (Table $table): void {
            $table
                ->paginationPageOptions([20, 50, 100]);
        });

For custom by devs :
    // AppServiceProvider.php
    // ...
    public function register(): void
    {
        // Register panel
        LunarPanel::register();

        // Override panel
        LunarPanel::panel(fn($panel) =>
            $panel->path('lunar')
                ->brandName('My custom name')
        )
        ->register();

        // Override default configuration
        Table::configureUsing(function (Table $table): void {
            $table
                ->paginationPageOptions([1, 5, 2]);
        });
       // ...

What do we do ? @glennjacobs

I would put the following in the Lunar service provider
Table::configureUsing(function (Table $table): void {
    $table
        ->paginationPageOptions([20, 50, 100])
        >defaultPaginationPageOption(20);
});

and then test that a developer can override this is their own app service provider.

@glennjacobs This will make all Filament tables (including non-Lunar ones) to use these pagination options.

@glennjacobs This will make all Filament tables (including non-Lunar ones) to use these pagination options.

Ah yes, that's a good point.

I would put the following in the Lunar service provider
Table::configureUsing(function (Table $table): void {
    $table
        ->paginationPageOptions([20, 50, 100])
        >defaultPaginationPageOption(20);
});

and then test that a developer can override this is their own app service provider.

That's it, i test override on AppServiceProvider works well

Use the resource extension, and a global in lunar panel manager. So that a global can be set there, and control for each resources


Create new form state for Enroll Account

Enroll account now has its own form state to allow more control over form labels and buttons, prompting user to set a password instead of changing a password.

I accidentally added other changes I am creating a separate PR for to the master branch, I will revert to clean this up and keep the PR's separate.

Alright, looking forward to this addition. 👍


dvc: 3.4.0 -> 3.5.0

Diff: https://github.com/iterative/dvc/compare/refs/tags/3.4.0...3.5.0
Changelog: https://github.com/iterative/dvc/releases/tag/3.5.0
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

2 packages failed to build:

python311Packages.dvclive
python311Packages.dvclive.dist

6 packages built:

dvc
dvc-with-remotes
dvc-with-remotes.dist
dvc.dist
python310Packages.dvclive
python310Packages.dvclive.dist

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

2 packages failed to build:

python311Packages.dvclive
python311Packages.dvclive.dist

6 packages built:

dvc
dvc-with-remotes
dvc-with-remotes.dist
dvc.dist
python310Packages.dvclive
python310Packages.dvclive.dist

Did upstream force-push the tag in the meantime?
https://hydra.nixos.org/build/227388333


Work On https://esm.sh/server

I will try writing tests for reejs later. Probably after some weeks :sweat_smile: .
I am looking the code atm for changing the bun target forward to node target instead of es2022

I will try writing tests for reejs later. Probably after some weeks sweat_smile . I am looking the code atm for changing the bun target forward to node target instead of es2022

Looks like its already using Node target.
I should publish my fixes and updates to reejs to complete this pr haha

LGTM, thanks @renhiyama this is big!


fix: 3D Touch will be responsed twice when the app is cold-launched

like this:
QuickActions.popInitialAction().then(quickActionsHandler);
DeviceEventEmitter.addListener('quickActionShortcut', quickActionsHandler);

quickActionsHandler will be called twice

@jordanbyron take a look at application:didFinishLaunchingWithOptions:
I think if application:didFinishLaunchingWithOptions: return NO, we should not handle the quick action. so we do not need to handle the quick action from the method application:didFinishLaunchingWithOptions:.

NO if the app cannot handle the URL resource or continue a user activity, otherwise return YES. The return value is ignored if the app is launched as a result of a remote notification.

@greedbell I agree that your proposed workflow of not handling the initial launch action would probably work, however there is a reason Apple has made the distinction between a cold start launch value vs a warm running app receiving and receiving a shortcut action. This choice was intentional and I don't think it's our place to break that behavior. For example, an app may have a deep stack of view layers that a shortcut action bypasses. The cold boot launch option allows the app to deep link directly into the desired screen without first displaying it's normal default view.
I think it makes the most sense if this library matches the same patterns that the underlying API provides and doesn't try to be smart or clever and change the way things are handled. So I think that means we should probably just close this PR and create a ticket to return the correct value (Which I think is NO from the didFinishLaunchingWithOptions method when a shortcut item is present at first launch. That should fix any double calls that we are seeing. What do you think?

@jordanbyron How about add a new method getQuickActionShortcut  to get shortcut action from application:performActionForShortcutItem:completionHandler, and the original method get shortcut action from application:didFinishLaunchingWithOptions:.
to skip quickActionsHandler be called twice, use it as follow
QuickActions.getQuickActionShortcut().then(quickActionsHandler);
DeviceEventEmitter.addListener('quickActionShortcut', quickActionsHandler);

Isn’t that what popInitialAction already does?
On Tue, Oct 9, 2018 at 7:12 AM Bell<EMAIL_ADDRESS>wrote:

@jordanbyron https://github.com/jordanbyron How about add a new method
getQuickActionShortcut to get shortcut action from
application:performActionForShortcutItem:completionHandler, and the
original method get shortcut action from
application:didFinishLaunchingWithOptions:.
to skip quickActionsHandler be called twice, use it as follow
QuickActions.getQuickActionShortcut().then(quickActionsHandler);
DeviceEventEmitter.addListener('quickActionShortcut', quickActionsHandler);
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jordanbyron/react-native-quick-actions/pull/62#issuecomment-428153058,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACe1ggaNYSRbNmECgMH086TkQzIVQ7Dks5ujISigaJpZM4Tp_zV
.

--
Jordan

@greedbell I spent a little time building a demo app and I don't think there is actually anything wrong with the library. The code is here, but you can see it at the URL below.
https://vimeo.com/294963456
The cold start pop action does not trigger the event listener. Everything works as expected. I'm going to close this PR now but if you can produce a counter example that recreates the double fire on launch feel free to open an issue and I'll review it. Thanks!


Merging

Hi,
Are you submit the PR by the mistake?

Hi,
Sorry for that. That was a mistake.
11 Haz 2024 Sal 13:27 tarihinde Geralt_of_Rivia @.***>
şunu yazdı:

Hi,
Are you submit the PR by the mistake?
—
Reply to this email directly, view it on GitHub
https://github.com/hustvl/4DGaussians/pull/140#issuecomment-2160388585,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKVK4P52RY4S5FALGJWYDDZG3GIZAVCNFSM6AAAAABJBV3ICWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRQGM4DQNJYGU
.
You are receiving this because you authored the thread.Message ID:
@.***>


Update hydra for commit draft api

Blocked by #384
Closes #381

@GeorgeFlerovsky Does it work? It was kinda draft AFAI remember.

Not quite. Still working on my fixes.


Typelead

Eta guys

You mean these guys https://github.com/typelead ?

Yes
On Aug 17, 2017 8:06 AM, "Erik Mossberg"<EMAIL_ADDRESS>wrote:

You mean these guys https://github.com/typelead ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/erkmos/haskell-companies/issues/7#issuecomment-323052680,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUlSuz79KIg_TBrpeUplvfATILquEJ1ks5sZCy5gaJpZM4O6KlO
.

thanks


Drone CI for arm64 native builds

There are 4 jobs for compilers gcc and clang and build system make and cmake.
I disabled lapack on cmake build as it was failing to build in cmake. (CMake build system gives a warning that openblas cmake supports only x86)

Here's an example build https://cloud.drone.io/isuruf/OpenBLAS/20

Added 2 more builds with arm32.

There are 48-core datacenter aarch64 CPUs being sold with promise of 64-core in near future.

There are 48-core datacenter aarch64 CPUs being sold with promise of 64-core in near future.

@martin-frbg, thanks for merging this. Did you enable drone CI?

I am just checking if I am allowed to enable this - I have also informed xianyi but did not receive a reply from him yet. Trying to logon to drone.io, I saw "organizational access" to OpenBLAS already checked in the mask but that may have been github reading my current profile. At least I can "activate" drone.io settings for my fork only, but get a "not found" error message when I try the same
for xianyi/OpenBLAS. So this may have to wait a bit before it can actually go live.

Xianyi tells me that he has enabled it now, but I do not see it come alive on PRs. Does this need any additional setup outside of what travis et al. require ?

I already actived it on https://cloud.drone.io/xianyi/OpenBLAS/

Still does not get invoked on new PRs. In my fork, I can access a "main" section in the drone.io settings which I do not see here (but it looks like the default settings should be appropriate already)

Looks like it gets invoked on actual commits alright, just not on pull requests.


Update README.md

Fixing links. Not sure why the old link style [text][link] is not converting, but text seems to do the trick.

Fixing in #2


[RecExplainer] Error in Dataset Preparation

Thank you for your excellent work!
When I run the command bash shell/preprocess_recmodel.sh, I encounter the following error. Could you please guide me on how to resolve it, how can I obtain the file unirec_raw_data/amazon_video_games_v3/train.tsv? I would appreciate your response.
FileNotFoundError: [Errno 2] No such file or directory: '~/RecAI/RecExplainer/data/unirec_raw_data/amazon_video_games_v3/train.tsv'

Thank you for your interest in our work!
To resolve the issue, please create the following folder:
~/RecAI/RecExplainer/data/unirec_raw_data/amazon_video_games_v3
Once the folder is created, the script should run without issues.


pg_dump missing table data after starting the container

We've been trying to backup a populated postgis database using pg_dump and haven't had much success.
So we went back to the simplest Dockerfile
FROM mdillon/postgis

After starting the container, we immediately bash'd in and ran pg_dump:
pg_dump -Upostgres -c postgres > dump

The dump file doesn't contain most of the useful seed tables, like state_lookup
We've tried many variations using pg_dumpall, specifying the schema using -n tiger, trying to grab specific tables, none have been successful.
Obviously this isn't a huge issue until we use the loader_generate scripts to pull in several download hours worth of data.  How do we back up the database inside this container?

I can confirm this behavior and I'm not sure what's going on. I can see that the tiger.state_lookup and other tables exist in a newly created instance of this image, but I also don't see it dumped in pg_dump.

Have you by any chance tested this outside of a Docker context?

I just tested this using PostGIS 2.2.2 and PostgreSQL 9.5.4 on my Mac from Homebrew and I got the same results.
From a bit of searching around, I believe the issue is that tables that are owned by an extension are not dumped by pg_dump since the extension is expected to recreate them. The pg_dump output does include the relevant CREATE EXTENSION statements from what I can see, both in the Docker case and the Homebrew case (in fact the dumps are functionally identical).

Closing this since there hasn't been any activity in almost a year and I'm not sure this is a problem with the image. I can reopen if we need to.


Help with finetuning

If I want to finetune the model with my own dataset, what file should I modify? and how can I make the model generate multi images in one turn?

You can create a new data loader in dataloader.py and use it for multiple image outputs.


Command + Shift + G switches desktops on macOS instead of opening on the current desktop

Problem: if you use multiple desktops (spaces) on macOS, then pressing Command + Shift + G will switch to the desktop that you originally opened the app on.
Expected behaviour: I would expect the app to open on the current desktop, regardless of which desktop it was originally opened on.
Workaround (updated): right click on the app, select Options, and then Assign To All Desktops.

thank you! i found this https://github.com/electron/electron/issues/8734 which might help

can you check if this is still an issue?

Seems to work now, yes, thank you! There is still some residual weird behaviour though:

In some cases the application doesn't appear, or seems to appear behind another application.
With multiple monitors it's not clear to me how it decides on which screen it appears.

it should appear on whatever is the most recent screen but i agree its. alittle funky


Fix GPG subkey verify (#30193)

Backport #30193 by @KN4CK3R
Fixes #30189
Can't verify subkeys if they are not loaded.

Not needed as per https://github.com/go-gitea/gitea/pull/30202#issuecomment-2028594802


Wrong classifier is silently ignored by coursier

steps
sbt version:1.3.5

Clone https://github.com/pdalpra/coursier-test
Go to the netty-epoll-direct folder, modify the netty dependency classifier to woops (any non existing classifier would do the trick too)
Run sbt update => Dependency resolution is successful (fails with Ivy)
Run sbt 'show fullClasspath' => Transitive dependencies are in the classpath, but not the dependency with the failed classifier (??)

problem
Dependency with invalid classifiers are silently ignored, but there is still a partial dependency resolution done by coursier (I suspect based on the default classifiers)
expectation
sbt with coursier should fail dependency resolution if the classifier could not be found.
notes

@pdalpra Thanks for the report! Could you also report this to coursier/coursier please?

Done!


Create a :%: modular arithmetic datatype

newtype (:%:) (int :: Type) (modulus :: Natural) = UnsafeMod int

This is the Mod type from #177 proof-of-concept
Motivation is to model things as what they are. For instance, in elliptic curve crypto, point coordinates are fixed width integer types in their (big-endian?) bit-representation. But the arithmetic functions that operate on them depend on a prime modulus which is smaller than their width. With (:%:) and the largeword library that can be represented directly.

Can we have modulus :: int instead to have a more general implementation (a factorization by an ideal with a single generator)?

Sure, it's possible to make the modulus be polykinded.

But there's a couple reasons we want modulus :: Natural for the case of modular arithmetic, including prime fields. The first is just mathematical that an integer modulus is invariant under sign change,
forall x y n : Integer.
x = y mod n <=> x = y mod (-n)

The second is just pragmatic, Haskell's Integer type doesn't promote to an Integer kind, with any useful operations. Natural on the other hand has type-level operations that let us implement primality checks and take logs, etc. We can implement our own Z kind. I even recently made one here. But it's really unnecessary for just modular arithmetic I think.

We can link int and kind with Demote in the link you provided, actually!

You can link int and kind with Demote kind ~ int, however, for many kinds you won't be able to construct a type of kind kind, at least not in an obvious way. For instance, you can't construct type Six :: Word8; type SixtyOne = 6 because type level numeric literals only works for Natural.
It makes sense to make the the modulus polykinded because we can interpret it in different ways for different ints, even non-integral types like perhaps polynomials. But focusing on the use case of modular arithmetic, I think that for instance Word8 :%: 6 contains exactly and only what type-level information is needed.

Consider the following type: Word8 :*: Ed25519_Scalar. How do we prevent anyone from constructing such datatypes?

I don't think it's important to prevent that 🤷


IdentityHub - Command line client

Feature #13
After #20 agera-edc/MinimumViableDataspace#151
Description
A command line application needs to be created which can act as Identity Hub client and this application is responsible for populating the Verifiable Credentials into participant's Identity Hub. This command line application internally uses IdentityHub API. A participant can be onboarded without the need of deploying it first.
MVD deployment pipeline should use this command line client in order to populate the Verifiable Credentials .
Acceptance Criteria

[ ] CLI is documented
[ ] Identity Hub command line client available to onboard participant.
[ ] Identity Hub command line client is able to push VCs to Identity Hub for onboarding
[ ] IH CLI is used in MVD deployment workflow in the participants onboarding process
[ ] Testing coverage.

Tasks

[ ] Implement Identity Hub CLI
[ ] Update docs and including local development instructions
[ ] Use Identity Hub CLI in MVD deployment workflow to push VCs signed by GAIA-X Authority to participants Identity Hub during the onboarding

Initial CLI will be already created in #21 to populate VCs into the Identity Hub


chunk 7 of CMP contribution to OpenSSL

Certificate Management Protocol (CMP, RFC 4210) extension to OpenSSL
Also includes CRMF (RFC 4211) and HTTP transfer (RFC 6712)
CMP and CRMF API is added to libcrypto, and the "cmp" app to the openssl CLI.
Adds extensive man pages and tests. Integration into build scripts.
7th chunk: CMP protection verification
in crypto/cmp/cmp_vfy.c and related files.
This PR includes also some improvements in code formatting (triggered by https://github.com/openssl/openssl/pull/10363) , logging and internal documentation.
Checklist

[x] documentation is added or updated
[x] tests are added or updated

@mattcaswell, I created this PR starting from the last version of https://github.com/mpeylo/cmpossl/pull/199. If successfully build I would like to ask you for a review.

The time exceeding travis job is probably not related to us.

moved some file updates between the commits, the final result is the same.

I've just pushed a new version that completes the cleanup of commits that @Akretsch did 8 hours before.
@mattcaswell, when doing the merge after this PR has been approved, I suggest not squashing these four commits into one:
commit 3c550e0fbcd69810de5cf85d71f29c278859ec90 (HEAD -> cmpossl_incremental7,  origin/cmpossl_fixup6_incremental7)
Author: Dr. David von Oheimb<EMAIL_ADDRESS>Date:   Fri Dec 13 19:45:53 2019 +0100

    chunk 7 of CMP contribution to OpenSSL: CMP message validation and related tests

commit 6d87fc4a1a23014a96364ea6352cf016fbb6967b
Author: Dr. David von Oheimb<EMAIL_ADDRESS>Date:   Fri Dec 13 20:07:08 2019 +0100

    fix various formatting nits in CMP contribution chunks 1-6 found by the new util/check-format.pl
    correct wording in doc, comments, and parameter names: self-signed -> self-issued where appropriate

commit 241a9a67b007124aa79816b25ab3a11049f074c2
Author: Dr. David von Oheimb<EMAIL_ADDRESS>Date:   Fri Dec 13 19:50:20 2019 +0100

    improve CMP logging after changes according to comments on CMP chunk7 preview

commit c5e413ee7c2bc69b44c2e3ca3e1972aaf97cebb9
Author: Dr. David von Oheimb<EMAIL_ADDRESS>Date:   Fri Dec 13 18:54:15 2019 +0100

    add internal doc files actually belonging to CMP contribution chunk 6

There is - like after the push before - one strange Travis CI failure, which I cannot reproduce locally:
80-test_ocsp.t ..................... ok
80-test_pkcs12.t ................... ok

The job exceeded the maximum time limit for jobs, and has been terminated.

For what ever reason, Travis keeps aborting its very last job on this PR at
80-test_ocsp.t ..................... ok
80-test_pkcs12.t ................... ok
The job exceeded the maximum time limit for jobs, and has been terminated.´

Does anyone understand why? This does not seem CMP related.

It seems to be a frequent and very annoying problem at the moment. Don't know why - but it's definitely not CMP related.

It's been plaguing the CI since https://github.com/openssl/openssl/commit/77fedcdc8cf5446354a1e7ff9123d8ada5b79b06, with one of the jobs running into a hard cutoff of 50min by Travis. See #10639 for a fix by @slontis.

Thanks @mattcaswell and @h-vetinari for your (comforting to me) comments!

Travis failures seem relevant. Also, already needs a rebase!

@mattcaswell I fixed the Travis failure and did a rebase.

@mattcaswell I fixed the Travis failure and did a rebase.

@Akretsch, when adding fixes to this PR please always use --fixup to make clear which commit is improved and to make sure that auto-squashing will work fine. I've done this by amending your recent commit (of Dec 19).

@mattcaswell (Back from vacation) I set all the review comments handled by @DDvO to resolved. Do you see further open points in this PR?

Aside from a couple of very minor nits I spotted, I'm ok with this.

Great - thanks a lot for finalizing your review!

rebased and review comment fixed

@bernd-edlinger We fixed all of your review comments. Is there something more we could do?

I've just rebased this CMP contribution chunk 7.
@bernd-edlinger, is there anything more to do from your perspective?
We should get this PR done soon.

Thanks @bernd-edlinger for your further comments!
I've already handled them.

Please have a look at the CI builds

Copyright is automatically patched up when a release is made, I wouldn't worry about copyright dates.  YMMV.

Please have a look at the CI builds

Ah, there was a mistake while manually resolving a merge conflict
in the usual culprit (util/libcrypto.num).
The respective Travis failures should be gone now.

@bernd-edlinger, CI succeeded and all comments resolved.

@bernd-edlinger, again all (new) comments addressed.

Thanks a lot @bernd-edlinger for very swiftly finishing your review
and the quick re-approval by @mattcaswell!
So looks like I can squash and merge this chunk after the usual one day grace period?

So looks like I can squash and merge this chunk after the usual one day grace period?

Looks like it - assuming no last minute problems from the CIs.

AppVeyor is always pretty slow, and this time it took even some 12 hours to complete (after presumably being busy grinding on other PRs), but finally it confirmed that the builds and tests pass.

I'll squash the commits already now in preparation of the later merge,
which among others should raise the chances that the merge
will be rewarded by that lovely purple-colored 'merged' icon :purple_heart:

Done squashing (and already adding the reviewer & pr info).
Do I need an explicit 'ready to merge' label before (potentially rebasing again) and pushing?

We do usually the final squash and rebase without pushing that to the PR again,
but directly to the openssl git server, once the grace period is over, the labels are just
optional, the final decision is human.
Howver now, I have problems to fetch the revision f431d686479a36131bdbbab23f9399c15d066637
from this pr which @mattcaswell originally approved,  so I am unable to double-check that the
squashing / re-basing did not introduce incorrectness.

We do usually the final squash and rebase without pushing that to the PR again,
but directly to the openssl git server, once the grace period is over,

Yes, but @mattcaswell recently asked me regarding PR #10667 to squash it before it was merged, and this had the nice effect that GitHub has been able to recognize the merge automatically, which is indicated by the purple 'Merged' label. I appreciate this, and others as well, and @beldmit even asked to 'incorporate the brilliant changes he made to the workflow' - see #11038

the labels are just optional, the final decision is human.

Good to know, thanks @bernd-edlinger.

However now, I have problems to fetch the revision f431d68
from this pr which @mattcaswell originally approved,

Yes, this indeed is a drawback. One could still follow up the commits via the link you gave and via its parent link etc, but this would be pretty cumbersome.
A workaround would be to save the original/unsquashed PR branch in a backup branch.

so I am unable to double-check that the squashing / re-basing did not introduce incorrectness.

Before force-pushing I had checked this using
git diff origin/cmpossl_incremental7

@Akretsch, if you still have the previous state of cmpossl_incremental7 locally, please push it as cmpossl_incremental7-orig such that we have it as backup/reference just in case.

cmpossl_incremental7-orig pushed

yes, that would be nice,
please do git reset --hard f431d686479a36131bdbbab23f9399c15d066637 before pushing that
since that was the originally approved version.  It should be available in your repo,
but I cannot pull if from github, although I know for sure, that revision is still in their database.

@bernd-edlinger, good idea to reset to the commit in question first.
This did not work our for @Akretsch (since he had fetched last on Feb 3rd), but for me.
I've force-pushed f431d686 to cmpossl_incremental7-orig now.

@DDvO  Have the CMP feature and CRMF feature  been completed? Are the test cases completed?

@DDvO Have the CMP feature and CRMF feature been completed? Are the test cases completed? When are these features planned for openssl 3.0.0?

@yangyangtiantianlonglong Next chunk is here. A  you may find their roadmap in this repo.

@yangyangtiantianlonglong, the state of the CMP contribution is shown and kept up-to-date at https://github.com/mpeylo/cmpossl/wiki#planning-and-current-status-of-the-contribution-chunks.

Where is this callback? I get:
test/cmp_vfy_test.c(72): error C2065: 'OSSL_CMP_print_cert_verify_cb': undeclared identifier

Looks like you had an inconsistent source tree or build.
The callback function is meanwhile called X509_STORE_CTX_print_verify_cb.


Realm instance persisting unexpectedly

Hello,
I'm developing an app that uses Realm in conjunction with user accounts. I've recently added this code for migration:
RLMRealm setSchemaVersion:1
                        forRealmAtPath:[GGRealmUtils realmPath]
                    withMigrationBlock:^(RLMMigration *migration, uint64_t oldSchemaVersion) {
        //migration code
}
[RLMRealm realmWithPath: realmPath]]

The app itself is user account based, so each realmPath is unique to the userId, and I can't just put this migration code in appdelegate since if a user logs out on their phone and has someone else log in, I would need to migrate for the new person as well, so I put it in my login controller and trigger it whenever someone logs in using the associated realmPath.
The issue I am having arises from writing to the user realm a second time while they are logged in, basically. Upon log in I make my first write transaction as follows:
// Instantiate realm object
RLMRealm *realm = [self realmForCurrentUser];

    [realm beginWriteTransaction];
    // write some objects using [realm addObject:]
    [realm commitWriteTransaction];

And at a certain point in the app after the user has done something I need to make another write transaction, so I run a variation on that same code again.
However, through testing and logging I've seen that the first realm instance gets deleted by ARC automatically as soon as the scope of my write transaction ends, but the second time I do it it persists for some reason and ARC doesn't clean it up, even though I don't have any references to it in my code. And so, if the user tries to log out and log back in, the migration code will through an exception:
Cannot set schema version for Realms that are already open.
because the realm instance is still cached.
Is there a method I can use to manually clear the realm cache? I'm very certain that I don't have any references to the realm (my code is pretty much the exact same for both the first and second write, minus the different objects to write), so why is the realm instance not being deleted from the cache?

@ezwu there's no publicly exposed way to manually clear the Realm cache, but it's really not something you should ever have to do. If there's already a Realm open, I suspect something still has a strong reference to it, and we'd be happy to have a look at help you debug that, either here or privately at<EMAIL_ADDRESS>If I could offer a suggestion, however, I'd advise just calling setSchemaVersion:ForRealmAtPath:withMigrationBlock: for every .realm file in the directory you store the Realm files in at program launch -- that way, there would be no possibility of trying to set the schema version for a Realm that is already open.

@segiddins thanks for the reply and the suggestion. I've checked my code for remaining references over and over but I just can't seem to find anything. I'm doing the bugged realm operations within a AWSTask continueWithBlock:^id(AWSTask *task) call, could that possibly be an issue?
If I were to migrate in the manner you described, what would happen in terms of schema version and migration when a new user logs in and I create a new realm? Would their realm automatically be updated to the post-migration version?

@ezwu you could just set the schema version when creating the realm for the first time.  If you're capturing any Realm objects in a block that's being bounced to a different queue, that could definitely be causing your RLMRealm to be retained, but it's hard to know for sure without seeing the code in question.

@segiddins Thanks immensely for your help. The queue issue doesn't seem to be the cause after some testing, since my other calls to realm occur on a background thread as well and don't cause me any problems.
I think what might be happening is that I'm potentially holding onto a reference of the object I am adding to the realm. Would that RLMObject's reference to the realm instance cause the realm to fail to deallocate? If that's the case, I think that that might be the reason for my issue.
I've tested two different ways of writing the necessary object to realm, the first being the original bugged way which is to call [realm addObject:] using my local reference to the object. The second way is to first pull from the online database Amazon dynamoDB, where the object is stored and then to add it to realm using the reference dynamoDB gives me, and that way doesn't cause the migration code to throw an exception.
As for your suggestion, could I just ask you to clarify how schema versions work? Specifically, my migration code sets, for specific objects, a new property that didn't exist on the old version to some default value. So if I were to open a new realm and write these objects with the new property already set to some other value into it, would the schema automatically update to reflect the fact that this property now exists or would it be some default value like 0 that would trigger the migration code to overwrite the value?

Yes, a persisted RLMObject has a strong reference to its RLMRealm.
We just talked over the API here in the office, and we think it makes sense to not throw an exception when using the setSchemaVersion API in the manner you are (aka. your use case should be supported), so disregard my wacky suggestions for working around our api :)

Awesome, I understand now. Thanks very much for you help!


Update to 0.5.1

0.5.1 is already pushed to rubygems.org, for the fix of the file
permissions.

Current coverage is 99.23% (diff: 100%)

Merging #43 into master will not change coverage

@@             master        #43   diff @@
==========================================
  Files            10         10
  Lines          1171       1171
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1162       1162
  Misses            9          9
  Partials          0          0

Powered by Codecov. Last update 90eff11...c155095


Fix lane name conflict when creating a new Fastfile

Fixes https://github.com/fastlane/fastlane/issues/5851

👍


[TOSFS #10] Implement rmdir API

Summary :memo:
Write an overview about it.
Details
Describe more what you did on changes.

(...)
(...)

Bugfixes :bug: (delete if dind't have any)

Checks

[ ] Closed #798
[ ] Tested Changes
[ ] Stakeholder Approval

@xianyinxin @openinx please take a look, when you have time.

@openinx @xianyinxin From my side, it seems all the concerns have been addressed. Please take another look.

@openinx I have fixed the commit signature issue. It needs gpg key.


How to install convential_changelog?

I want to use conventional_changelog on my local environment, when I'm pushing through the GitHub desktop (on my windows machine).
I'm not a professional open source programmer, and it's not obvious to me how to make it work (maybe like I'm used to do, through trials and errors).
I'm not sure about how to use it. Maybe I have to install the smichard/conventional_changelog in my local repo. Or maybe I can install it globally?
Another question is, if there is possibly to use generate_changelog_local.sh without installing the hole package.
I will be very happy to getting know how to use this script in a easy way.
I'm really sorry that I have to ask this silly question.
PS! I have no experience or knowledge using .github/workfows.

https://www.opensourcerers.org/2024/03/25/enhancing-code-project-documentation-through-automated-changelogs/
Thank you for reaching out and for your interest in using Conventional Changelog! Here are a few ways you can use the tool in your local environment:
Native Usage on Linux
If you have access to a Linux environment, you can run the script natively. Simply navigate to your repository directory and execute:
./generate_changelog_local.sh

This will generate the changelog directly from your commit history.
Using a Container Engine on Windows
Since you're using Windows, the recommended approach is to use a container engine like Docker or Podman. This ensures a consistent environment without needing to install dependencies directly on your machine.

Build the Container Image:
First, build the container image using the provided Dockerfile. Open a terminal (e.g., Command Prompt, PowerShell) and run:

podman build -t conventional_changelog -f Dockerfile
# Or if using Docker
docker build -t conventional_changelog -f Dockerfile

Run the Container:
Then, run the container and mount your local repository directory to the container:

podman run -it --rm -v "$(pwd):/repo" conventional_changelog sh
# Or if using Docker
docker run -it --rm -v "$(pwd):/repo" conventional_changelog sh

Execute the Script Inside the Container:
Inside the container, navigate to the mounted repository directory and execute the script:

cd repo
./generate_changelog_local.sh

Using GitHub Actions
If you'd like to automate the process so that the changelog updates every time you push changes, you can use GitHub Actions. Here’s a quick overview:
Add a Workflow Configuration:
Create a new file in your repository at .github/workflows/generate_changelog.yml and add the following configuration:
name: Generate Changelog

on:
  push:
    branches: [ main ]

jobs:
  changelog:
    runs-on: ubuntu-latest
    name: Generate and Commit Changelog

    steps:
    - name: Checkout Repository
      uses: actions/checkout@v4

    - name: Generate Changelog
      uses<EMAIL_ADDRESS>      with:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

    - name: Set Git User Info
      run: |
        git config user.name 'GitHub Actions Bot'
        git config user.email<EMAIL_ADDRESS>
    - name: Commit Changelog
      run: |
        git add CHANGELOG.md
        git commit -m "docs: :robot: changelog file generated" || echo "No changes to commit"
        git push

This setup ensures that every time you push changes to the main branch, the changelog will be automatically updated and committed.
Conclusion
I hope this helps! Feel free to try these methods and see which one fits best with your workflow. If you run into any issues or have more questions, don’t hesitate to ask. We're here to assist you in making the best use of Conventional Changelog.


Bugs: WMSTilelayer not working

Hi,  I got a map from jimatt with wms.
return U.Map(
        controller: MapController(),
        center: [-6.175520973390827,<PHONE_NUMBER>2001038],
        zoom: 14,
        base: U.WMSTileLayer(
          "https://jimatt.com/wms?",
          format: "image/png",
          layers: "basemap",
          maxZoom: 21,
          transparent: false,
          crs: CRS.EPSG3857,
          additionalOptions: {'tiled': true, "PANE": 'labels'},
        ));

then i got an error like this
════════ Exception caught by widgets library ═══════════════════════════════════
The following _TypeError was thrown building JimattPage(dirty, state: _JimattPageState#7eaf5):
type "_InternalLinkedHashMap<String, Object> "is not a subtype of type "Map<String, String>?"

The relevant error-causing widget was
JimattPage
lib/main.dart:31
When the exception was thrown, this was the stack
#0      U.WMSTileLayer (package:universe/src/u.dart:4223:28)
#1      _JimattPageState.build
package:example_ddd/…/jimatt/jimatt_page.dart:43
#2      StatefulElement.build
package:flutter/…/widgets/framework.dart:4691
#3      ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4574
#4      StatefulElement.performRebuild
package:flutter/…/widgets/framework.dart:4746
...
════════════════════════════════════════════════════════════════════════════════

I know almost nothing about this ... so take this with a grain of salt.  And I've just in the last hour starting looking at Universe and map providers.  So I thought I'd take a look at your problem mostly as a learning experience.
When I go to the jimatt.com site and inspect the URL they request for a map image, I see something like this:
https://jimatt.com/wms?service=WMS&request=GetMap&layers=basemap&styles=&format=image%2Fjpeg&transparent=false&version=1.1.1&width=256&height=256&srs=EPSG%3A3857&bbox=11896047.58607855,-687321.7583403048,11897270.578531114,-686098.7658877411
However, I don't see similar parameters, such as lat/lon, being provided in your U.Map call.  As stated in the README:
U.Map(
  center: [51.555158, -0.108343],
  base: U.TileLayer('https://{s}.tile.opentopomap.org/{z}/{x}/{y}.png',
    attribution: 'Map data: © OpenStreetMap contributors, SRTM | Map style: © OpenTopoMap',
    maxZoom: 17,
  ),
)

You are missing the {z}, {x} and {y} parameters, as well as likely other parameters required by jimatt.com.  I'm guessing that the malformed URL is resulting in a non-image, such as when I hand type in a URL that is lacking the lat/lon (etc) I get a ERR_INVALID_RESPONSE.
There are likely better ways to debug this ... but at a minimum, try building this using Chrome and inspect the network request and work on getting your request to submit a valid URL?
Hope this helps.  Good luck!

I know almost nothing about this ... so take this with a grain of salt. And I've just in the last hour starting looking at Universe and map providers. So I thought I'd take a look at your problem mostly as a learning experience.
When I go to the jimatt.com site and inspect the URL they request for a map image, I see something like this:
https://jimatt.com/wms?service=WMS&request=GetMap&layers=basemap&styles=&format=image%2Fjpeg&transparent=false&version=1.1.1&width=256&height=256&srs=EPSG%3A3857&bbox=11896047.58607855,-687321.7583403048,11897270.578531114,-686098.7658877411
However, I don't see similar parameters, such as lat/lon, being provided in your U.Map call. As stated in the README:
U.Map(
  center: [51.555158, -0.108343],
  base: U.TileLayer('https://{s}.tile.opentopomap.org/{z}/{x}/{y}.png',
    attribution: 'Map data: © OpenStreetMap contributors, SRTM | Map style: © OpenTopoMap',
    maxZoom: 17,
  ),
)

You are missing the {z}, {x} and {y} parameters, as well as likely other parameters required by jimatt.com. I'm guessing that the malformed URL is resulting in a non-image, such as when I hand type in a URL that is lacking the lat/lon (etc) I get a ERR_INVALID_RESPONSE.
There are likely better ways to debug this ... but at a minimum, try building this using Chrome and inspect the network request and work on getting your request to submit a valid URL?
Hope this helps. Good luck!

I already clone the code and check the error, then i try to change to fix it. It error because the U.WMSTileLayer use const <String,dynamic>{}. But in the L.WMSTileLayerOptions additionalOptions use <String,String> that make this error

type "_InternalLinkedHashMap<String, Object> "is not a subtype of type "Map<String, String>?"

and the next error is on the _baseUrl on param service it use & at the begining that make the jimaat map not show and i check the url it like this

https://jimatt.com/wms&service=WMS&request=GetMap&layers=basemap&styles=&format=image%2Fjpeg&transparent=false&version=1.1.1&width=256&height=256&srs=EPSG%3A3857&bbox=11896047.58607855,-687321.7583403048,11897270.578531114,-686098.7658877411

then i fix it from service i change into ?service=WMS and then it fix everything. and i can use the jimatt map.
Btw thanks for the help

@veldrict please use the latest version I just update (universe v 1.1.0-nullsafety)
I've also included Jimatt as the example of WmsMap. You can see it at demo apk dan check the code [here].(https://github.com/salkuadrat/universe/blob/master/example/lib/src/map_provider/wms.dart).


Feature:  update API to use HTTP API and new service integrations

Migrate API implementation to use HTTP API and new service integrations. Potentially look at integrating EventBridge into the solution.

Reviewed, and put on hold for now.


feat(core): refresh store when core version is bump up to major version

This behavior should be programmed more accurately.
When breaking change occurs, I will support this.
For now, there should be no such behavior.


Problem using NODE_ENV and Babel

Since a couple of days I have trouble running npm scrips that were working before. I've tried to narrow it down to a minimal example:
package.json
{
  "name": "babel-exp",
  "version": "1.0.0",
  "main": "index.js",
  "license": "MIT",
  "scripts": {
    "start1": "NODE_ENV=foo babel-node src/index",
    "start2": "BABEL_ENV=foo babel-node src/index"
  },
  "dependencies": {
    "babel-cli": "^6.24.1",
    "babel-preset-env": "^1.5.1"
  }
}

.babelrc
{
  "env": {
    "foo": {
      "presets": ["env"]
    }
  }
}

src/index.js
import { hello, bye } from './sayings'

console.log('hello = ', hello);

src/sayings.js
export const hello = 'hello'
export const bye = 'bye'

Running start1 with either npm or yarn results in: SyntaxError: Unexpected token import
start2 logs hello =  hello correctly
However, if I use OSX Terminal, both scripts run just fine.
node: v7.10.0
yarn: v0.24.6
npm: 4.1.1

Well, in my original project this got resolved when I removed a folder that jest uses as a cache. I am not sure what is going on, but you can probably ignore this issue.


Fix finishing

This should be used for main service. Other which are not important can use that without because that prevent shutdown of the add-on in every error case

Updated. I think it's just an example and people copy that, so it should get copy correctly for the main use case to run a program


Update shaken-urls.txt

@rmhrisk Tests seem to be failing, but the commit seems correct.

When running the TestLintUrl_HttpStatus503 test, which sends a request to https://app.connexcs.com/api/stir-shaken/cert/41.crt, it now returns a 404 status code instead of the previously returned 503. The test needs to be updated to reflect this change.


Show contract symbol in position

Resolves https://github.com/itchysats/itchysats/issues/2759
Looks like this when extra info is enabled:

vs disabled

a comment on the looks: can we center the heading (I know it's centered on one of the elements already), but it doesn't look too good; it should be center of the tile itself).

a comment on the looks: can we center the heading (I know it's centered on one of the elements already), but it doesn't look too good; it should be center of the tile itself).

I tried, but that messes with the whole layout...

update:

bors r+


8/6/2019 Publish

Docs Build status updates of commit 01d1a56:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-conceptual/azureadps-1.0/install-msonlinev1.md
:warning:Warning

Details

docs-conceptual/azureadps-1.0/overview.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0/install-adv2.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0/ad-pshell-v2-version-history.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0/working-with-licenses.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0/Cannot-find-object.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0/Working-with-Administrative-Units.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0/using-extension-attributes-sample.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0-preview/Cannot-find-object.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0-preview/install-adv2.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0-preview/using-extension-attributes-sample.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0-preview/working-with-licenses.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0-preview/Working-with-Administrative-Units.md
:warning:Warning

Details

azureadps-2.0-preview/AzureAD/AzureADPreview.md
:white_check_mark:Succeeded

azureadps-2.0-preview/AzureAD/Get-AzureADMSRoleAssignment.md
:white_check_mark:Succeeded

azureadps-2.0-preview/AzureAD/Get-AzureADMSRoleDefinition.md
:white_check_mark:Succeeded

azureadps-2.0-preview/AzureAD/New-AzureADMSRoleAssignment.md
:white_check_mark:Succeeded

azureadps-2.0-preview/AzureAD/New-AzureADMSRoleDefinition.md
:white_check_mark:Succeeded

azureadps-2.0-preview/AzureAD/Remove-AzureADMSRoleAssignment.md
:white_check_mark:Succeeded

azureadps-2.0-preview/AzureAD/Remove-AzureADMSRoleDefinition.md
:white_check_mark:Succeeded

azureadps-2.0-preview/AzureAD/Set-AzureADMSRoleDefinition.md
:white_check_mark:Succeeded

docs-conceptual/azureadps-1.0/install-msonlinev1.md

Line 20: [Warning] Link https://docs.microsoft.com/en-us/powershell/azuread/v2/azureactivedirectory contains locale code en-us. For localizability, remove en-us from links to Microsoft sites. For more information, see https://aka.ms/LocaleSpecificLinks.
Line 40: [Warning] Link https://docs.microsoft.com/en-us/azure/active-directory/active-directory-accessmanagement-groups-settings-cmdlets contains locale code en-us. For localizability, remove en-us from links to Microsoft sites. For more information, see https://aka.ms/LocaleSpecificLinks.
Line 90: [Warning] Link https://msdn.microsoft.com/en-us/library/azure/dn194123(v=azure.98).aspx contains locale code en-us. For localizability, remove en-us from links to Microsoft sites. For more information, see https://aka.ms/LocaleSpecificLinks.
[Suggestion] Missing attribute: title. Add a title string to show in search engine results.

docs-conceptual/azureadps-1.0/overview.md

Line 6: [Warning] Link https://docs.microsoft.com/en-us/powershell/azuread/v2/azureactivedirectory contains locale code en-us. For localizability, remove en-us from links to Microsoft sites. For more information, see https://aka.ms/LocaleSpecificLinks.
Line 35: [Warning] Link https://msdn.microsoft.com/en-us/library/azure/dn194123(v=azure.98).aspx contains locale code en-us. For localizability, remove en-us from links to Microsoft sites. For more information, see https://aka.ms/LocaleSpecificLinks.
[Suggestion] Missing attribute: title. Add a title string to show in search engine results.

docs-conceptual/azureadps-2.0/install-adv2.md

Line 69: [Warning] Link https://msdn.microsoft.com/en-us/library/5a4x27ek.aspx contains locale code en-us. For localizability, remove en-us from links to Microsoft sites. For more information, see https://aka.ms/LocaleSpecificLinks.
Line 129: [Warning] Link https://msdn.microsoft.com/en-us/powershell/scripting/getting-started/getting-started-with-windows-powershell contains locale code en-us. For localizability, remove en-us from links to Microsoft sites. For more information, see https://aka.ms/LocaleSpecificLinks.
[Suggestion] Missing attribute: title. Add a title string to show in search engine results.

docs-conceptual/azureadps-2.0/ad-pshell-v2-version-history.md

Line 96: [Warning] Link https://docs.microsoft.com/en-us/azure/active-directory/privileged-identity-management/ contains locale code en-us. For localizability, remove en-us from links to Microsoft sites. For more information, see https://aka.ms/LocaleSpecificLinks.
Line 105: [Warning] Link https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-reference-trustframeworks-defined-ief-custom#understand-trust-framework-policies contains locale code en-us. For localizability, remove en-us from links to Microsoft sites. For more information, see https://aka.ms/LocaleSpecificLinks.
Line 112: [Warning] Link https://docs.microsoft.com/en-us/azure/active-directory/reports-monitoring/ contains locale code en-us. For localizability, remove en-us from links to Microsoft sites. For more information, see https://aka.ms/LocaleSpecificLinks.

docs-conceptual/azureadps-2.0/working-with-licenses.md

Line 15: [Warning] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. See https://aka.ms/MarkdownHeadings for more information.
[Suggestion] Missing attribute: title. Add a title string to show in search engine results.

docs-conceptual/azureadps-2.0/Cannot-find-object.md

Line 28: [Warning] Multiple H1s are not allowed. You can only have one top-level heading. See https://aka.ms/MarkdownHeadings for more information.
[Suggestion] Missing attribute: title. Add a title string to show in search engine results.

docs-conceptual/azureadps-2.0/Working-with-Administrative-Units.md

Line 20: [Warning] A space is required after the hash (#) in H1. See https://aka.ms/MarkdownHeadings for more information.
Line 20: [Warning] Multiple H1s are not allowed. You can only have one top-level heading. See https://aka.ms/MarkdownHeadings for more information.
[Suggestion] Missing attribute: title. Add a title string to show in search engine results.

docs-conceptual/azureadps-2.0/using-extension-attributes-sample.md

Line 37: [Warning] Link https://msdn.microsoft.com/en-us/library/azure/ad/graph/howto/azure-ad-graph-api-directory-schema-extensions contains locale code en-us. For localizability, remove en-us from links to Microsoft sites. For more information, see https://aka.ms/LocaleSpecificLinks.
[Suggestion] Missing attribute: title. Add a title string to show in search engine results.

docs-conceptual/azureadps-2.0-preview/Cannot-find-object.md

Line 28: [Warning] Multiple H1s are not allowed. You can only have one top-level heading. See https://aka.ms/MarkdownHeadings for more information.
[Suggestion] Missing attribute: title. Add a title string to show in search engine results.

docs-conceptual/azureadps-2.0-preview/install-adv2.md

Line 69: [Warning] Link https://msdn.microsoft.com/en-us/library/5a4x27ek.aspx contains locale code en-us. For localizability, remove en-us from links to Microsoft sites. For more information, see https://aka.ms/LocaleSpecificLinks.
Line 132: [Warning] Link https://msdn.microsoft.com/en-us/powershell/scripting/getting-started/getting-started-with-windows-powershell contains locale code en-us. For localizability, remove en-us from links to Microsoft sites. For more information, see https://aka.ms/LocaleSpecificLinks.
[Suggestion] Missing attribute: title. Add a title string to show in search engine results.

docs-conceptual/azureadps-2.0-preview/using-extension-attributes-sample.md

Line 37: [Warning] Link https://msdn.microsoft.com/en-us/library/azure/ad/graph/howto/azure-ad-graph-api-directory-schema-extensions contains locale code en-us. For localizability, remove en-us from links to Microsoft sites. For more information, see https://aka.ms/LocaleSpecificLinks.
[Suggestion] Missing attribute: title. Add a title string to show in search engine results.

docs-conceptual/azureadps-2.0-preview/working-with-licenses.md

Line 15: [Warning] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. See https://aka.ms/MarkdownHeadings for more information.
[Suggestion] Missing attribute: title. Add a title string to show in search engine results.

docs-conceptual/azureadps-2.0-preview/Working-with-Administrative-Units.md

Line 20: [Warning] A space is required after the hash (#) in H1. See https://aka.ms/MarkdownHeadings for more information.
Line 20: [Warning] Multiple H1s are not allowed. You can only have one top-level heading. See https://aka.ms/MarkdownHeadings for more information.
[Suggestion] Missing attribute: title. Add a title string to show in search engine results.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Fix initialize signature for CSV::MalformedCSVError

Motivation
Fixes this error:
CSV::MalformedCSVError.new("message", 1) # error: Too many arguments provided for method Exception#initialize. Expected: 0..1, got: 2

[sorbet.run]
As per the documentation,  CSV::MalformedCSVError#initialize takes two arguments.
Test plan

See included automated tests.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_KxVg8ZYl0YvkHW
→ https://go/builds/bui_KxVgKAJxjmW971


[contact] add faces + photo trainings

https://pehapkari.cz/uploads/images//jan_mikes.jpg
https://avatars2.githubusercontent.com/u/924196?s=460&v=4

Done :+1: