[Bug] Last commit date

Gitea version (1.12.0+dev-336-g530f8963f):
Git version: 1.12.0 Dev
Operating system: Unknown
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite
[x] Not relevant

Can you reproduce the bug at https://try.gitea.io:

[x] Yes (https://try.gitea.io/TimerWolf/MarkdownBug/commits/branch/master)
[ ] No

Log gist:

[x] Not relevant

Description
As my native language is swedish the whole gitea page will be in swedish and that's nice, but the commit date don't seems to fallow the way the date is written here in sweden and i would imagine that this is the case for a lot languages.
I don't know if this is a bug, just bring it up to the surface and see if it worth notice, i mean the tooltip is not translated either.
Screenshots

You can change that on app.ini on section [ui]

@lunny: can you be a bit more specific? I can't find anywhere where you change the "Tue" to "Tis" that would be in my native language.

https://docs.gitea.io/en-us/config-cheat-sheet/#time-time

I'm not sure you can translate the names of the days from our confic. If anything, I'd try setting LC_TIME=sv_SE.utf8 in the environment before gitea runs (e.g. in the script used to launch it).


Any plans to have a Julia package?

Congratulations on the outstanding work!!
I wondered if there are any plans on having this package as a Julia package as well?
Cheers,
Daniel

Hey @dpabon!
Thank you! :D
Actually, yes!!! @MartinuzziFrancesco is working on that ;) the repo is private atm, but keep an eye on https://github.com/awesome-spectral-indices
Best,
David

I am planning around an end to summer release more or less so yeah, do watch this space for updates!

Closing this issue as SpectralIndices.jl has been released! :partying_face:


[cpprealm] New Port

[x] Changes comply with the maintainer guide.
[x] The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.
[x] Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all find_package calls are REQUIRED, are satisfied by vcpkg.json's declared dependencies, or disabled with CMAKE_DISABLE_FIND_PACKAGE_Xxx.
[x] The versioning scheme in vcpkg.json matches what upstream says.
[x] The license declaration in vcpkg.json matches what upstream says.
[x] The installed as the "copyright" file matches what upstream says.
[x] The source code of the component installed comes from an authoritative source.
[x] The generated "usage text" is accurate. See adding-usage for context.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is in the new port's versions file.
[ ] Only one version is added to each modified port's versions file.

Please follow the robot prompts to sign Contributor License Agreement(CLA).

@microsoft-github-policy-service agree [company="MongoDB"]

@microsoft-github-policy-service agree company="MongoDB"

Usage test passed with x64-windows triplet.

All dependencies have to come from the registry and no port should vender their own dependencies. If they are not in the registry, they should be added in separate PRs per port.
So far I see this port providing the following libraries under various conditions:

realm-cpp
realm-core
Catch2
sha1
sha-2

We should also be using upstreams name unless it is not in repology.org. Why rename the port from realm-cpp to cpprealm?
I also see you are using string replacement to patch over some of the headers? Can you explain your rationale?

Hi @JavierMatosD
Thank you for your feedback. I understand your concerns. To address the former, I will close this PR and first submit a new one specifically for the realm-core dependency, followed by another for realm-cpp.
Our target name is cpprealm, while the repo is named realm-cpp. Changing this would be a breaking change for us. We are not currently in repology.org.
The string replacements in the headers are necessary because we use std::aligned_storage to encapsulate realm-core types within our bridge classes. Since we cannot publicly expose these types, we must compute and inject the correct size and alignment values during installation. This requirement leads us to modify the bridge_types.hpp header as part of our build process.


Display for HString is not infallible

The Rust documentation says:

…a formatting implementation must and may only return an error if the passed-in Formatter returns an error. This is because, contrary to what the function signature might suggest, string formatting is an infallible operation.

but if an HString contains unpaired surrogates, its Display::fmt implementation will return a std::fmt::Error instead (and to_string() will panic). I think in this case it would be quite reasonable for the formatting to work like String::from_utf16_lossy instead.
Whatever the desired behaviour is, there should be tests to confirm the panic or replacement characters.

Looks like the standard library just replaces invalid code points while displaying Wtf8, the internal representation of Rust OsStrings on Windows. Maybe it would be a good idea to do the same, mimicking the behavior of OsStrings and Paths? Maybe we could add a method to get an &OsStr view of an HString and just delegate Display to it?

Does it make more sense to not implement Display on HString, since HString just a wide-encoded version of Rust's OsString? IMO HString should only implement Debug, and a method like Path::display should be used to get something that implement Display.

Sorry for the delay - lost track of this one. There's a fix here: #1915

Looks good to me, for what it’s worth.


Tweaks to add remote selenium driver

The changes enable usage of driver.remote() in selenium for remote execution.

I think it looks mostly good to me, except the one nit on the assertion.
I'll have to test it myself some time—I didn't know you could do this with Selenium!—but otherwise thank you for the contribution and I'll try to merge it quickly.

Hold up. Keep this in pull. I see a few issues that I'd like to merge as well.

If you want to test
docker run -d -p 4444:4444 -p 7900:7900 -e SE_NODE_MAX_SESSIONS=8 --shm-size="4g" --name="sel" selenium/standalone-chrome

All good now. Tested with my workflow.
If you guys want to test:
docker run -d -p 4444:4444 -p 7900:7900 -e SE_NODE_MAX_SESSIONS=8 --shm-size="4g" --name="SEL" selenium/standalone-chrome

ef run_agent(instructions, proxy, config_arguements):

    agent = GPTSeleniumAgent(instructions,
                             remote_url=http://localhost:4444,
                             chrome_options=chrome_options,
                             user_data_dir=config_arguements.user_data_dir,
                             headless=True)
    agent.run()

I'll have to test it myself some time—I didn't know you could do this with Selenium!—but otherwise thank you for the contribution and I'll try to merge it quickly.

Yeah maintaining selenium, chrome, and chromedriver is a pain. TThis is easier to just fireoff and run from a remote location.

Taking a look now.

All good now. Tested with my workflow.
If you guys want to test
Selenium Remote Driver
docker run -d -p 4444:4444 -p 7900:7900 -e SE_NODE_MAX_SESSIONS=8 --shm-size="4g" --name="SEL" selenium/standalone-chrome

Calling the agent
def run_agent(instructions, config_arguements):

    agent = GPTSeleniumAgent(instructions,
                             remote_url=http://localhost:4444,
                             user_data_dir=config_arguements.user_data_dir,
                             headless=True)
    agent.run()

Hey @rapatel0 I tried this and got the following error: selenium.common.exceptions.SessionNotCreatedException: Message: Could not start a new session. Error while creating session with the driver service. Stopping driver service: Could not start a new session. Response code 500. Message: unknown error: cannot create default profile directory.
Once I can replicate it working then I'll merge and update the package.

Thanks @rapatel0, just updated the package. 0.2.51. Appreciate the update, this was cool to try out.


Redesigning Ui and improving the Frontend of About us Page

As we can see the about us page doesnt look good, i want to redesign it and make it more appealing.
Can you assign this issue to me under GSSOC 24.

I have worked on this @codervivek5 Can you assign me under GSSOC 24?

Hi, i am interested to work on this part, please assign it to me.


cannot find type 'Process' in scope when compiling

Having trouble getting started. I keep getting the following errors in my CircleCI test step. My Package.swift file is copied at the bottom.
❌  /Users/distiller/output/.build/checkouts/swift/Sources/DangerShellExecutor/ShellExecutor.swift:110:51: cannot find type 'Process' in scope

                          outputFile: String?) -> Process {
                                                  ^~~~~~~

❌  /Users/distiller/output/.build/checkouts/swift/Sources/DangerShellExecutor/ShellExecutor.swift:121:20: cannot find 'Process' in scope

        let task = Process()
                   ^~~~~~~

import PackageDescription

let package = Package(
    name: "LuboTvOSNetworkingKit",
    platforms: [
        .iOS(.v10), .tvOS(.v12), .watchOS(.v4)
    ],
    products: [
        // Products define the executables and libraries produced by a package, and make them visible to other packages.
        .library(name: "LuboTvOSNetworkingKit", targets: ["LuboTvOSNetworkingKit"]),
        .library(name: "DangerDeps", type: .dynamic, targets: ["DangerDependencies"]) //dev
    ],
    dependencies: [
        // Dependencies declare other packages that this package depends on.
        .package(name: "LuboNetworking", url: "https://github.com/lubotv/apple-networking-core.git", from: "31.1.1"),
        .package(name: "danger-swift", url: "https://github.com/danger/swift.git", from: "1.0.0") //dev
        /*.package(name: "DangerXCodeSummary", url: "https://github.com/f-meloni/danger-swift-xcodesummary", from: "2.0.0")*/
    ],
    targets: [
        // Targets are the basic building blocks of a package. A target can define a module or a test suite.
        // Targets can depend on other targets in this package, and on products in packages which this package depends on.
        .target(name: "LuboTvOSNetworkingKit", dependencies: ["LuboNetworking"]),
        .target(name: "DangerDependencies",
                dependencies: ["Danger"],
                path: "Sources/DangerDependencies", sources: ["Fake.swift"]), //dev
        .testTarget(name: "LuboTvOSNetworkingKitTests", dependencies: ["LuboTvOSNetworkingKit"])
    ]
)

Which environment are you using on CI?

XCode 12.0.0
The CI step in question looks like this:
swift package generate-xcodeproj
swift package update
xcodebuild build -sdk iphoneos -scheme 'LuboTvOSNetworkingKit-Package'
xcodebuild test -destination 'name=iPhone 8' -scheme 'LuboTvOSNetworkingKit-Package' -enableCodeCoverage YES -derivedDataPath .build/derivedData | xcpretty && exit ${PIPESTATUS[0]}

So I think I know what is the issue, Danger uses Process that is not available on iOS/tvOS and watchOS.
My suggestion would be to make a Package.swift only for Danger, in a separated folder.
You can still run it as you were in the main folder with https://github.com/danger/swift#current-working-directory  so in CI you would have something like cd Danger && swift run danger-swift ci --cwd .

Closing this issue, because should be answered, if you still have an issue with it feel free to re open it

Closing this issue, because should be answered, if you still have an issue with it feel free to re open it


showOnFocus not working

I am trying to prevent the calendar from popping up unless the user has clicked the calendar button. So far I have not been successful. can anyone verify that I have set this up correctly?

	<input name="Customer.DateOfBirth" class="form-control" id="Customer_DateOfBirth" type="text" placeholder="Birth" value="" data-fv-field="Customer.DateOfBirth">

$('.date').datepicker(
	{
		format: 'mm/dd/yyyy',
		autoclose: true,
		todayHighlight: true,
		showOnFocus: false,
		showOn: "button"
	}
);

I have verified that the showOnFocus is in the options that are passed.

my bad... I had the wrong js source.


Fix a typo in the error page

fixes #756

Coverage remained the same at 100.0% when pulling 1c3cb4434cfdeff28f7c793fa2285dbca787c5e9 on 756-typo into 267880f682e79af5d7789d0d79cafc142e66fd8b on master.


Both width and height of the pattern should have bigger than 2 in function cvFindChessboardCorners

I changed the width and height of chessboard in 'config/wizard.xml'. But when I chose the 0(initial images capture) mode, this code was aborted. Could you give me some help?

Hi @monroe-git , thanks for your interest in our work.
What width and height of chessboard did you change? Maybe OpenCV does not allow that? Moreover, I noticed that you are using OpenCV 3.2. Since I started developing this tool a very long time ago and I was using 2.4.11, I am not sure if there are some major changes in OpenCV since then. This might be another reason.


Redis cluster connection error while trying to use as cache

WARN [ForkJoinPool-1-worker-22] org.apache.druid.client.cache.AbstractRedisCache - Exception pushing item to cache redis.clients.jedis.exceptions.JedisNoReachableClusterNodeException: No reachable node in cluster         at redis.clients.jedis.JedisSlotBasedConnectionHandler.getConnection(JedisSlotBasedConnectionHandler.java:57) ~[jedis-2.9.0.jar:?]         at redis.clients.jedis.JedisSlotBasedConnectionHandler.getConnectionFromSlot(JedisSlotBasedConnectionHandler.java:74) ~[jedis-2.9.0.jar:?]         at redis.clients.jedis.JedisClusterCommand.runWithRetries(JedisClusterCommand.java:116) ~[jedis-2.9.0.jar:?]         at redis.clients.jedis.JedisClusterCommand.runBinary(JedisClusterCommand.java:60) ~[jedis-2.9.0.jar:?]         at redis.clients.jedis.BinaryJedisCluster.setex(BinaryJedisCluster.java:268) ~[jedis-2.9.0.jar:?]         at org.apache.druid.client.cache.RedisClusterCache.putToRedis(RedisClusterCache.java:46) ~[druid-redis-cache-0.20.0.jar:0.20.0]         at org.apache.druid.client.cache.AbstractRedisCache.put(AbstractRedisCache.java:84) [druid-redis-cache-0.20.0.jar:0.20.0]         at org.apache.druid.client.cache.ForegroundCachePopulator$1.after(ForegroundCachePopulator.java:114) [druid-server-0.20.0.jar:0.20.0]         at org.apache.druid.java.util.common.guava.WrappingYielder.close(WrappingYielder.java:98) [druid-core-0.20.0.jar:0.20.0]         at org.apache.druid.java.util.common.guava.MergeSequence.makeYielder(MergeSequence.java:146) [druid-core-0.20.0.jar:0.20.0]         at org.apache.druid.java.util.common.guava.MergeSequence.toYielder(MergeSequence.java:105) [druid-core-0.20.0.jar:0.20.0]         at org.apache.druid.java.util.common.guava.ParallelMergeCombiningSequence$ResultBatch.fromSequence(ParallelMergeCombiningSequence.java:869) [druid-core-0.20.0.jar:0.20.0]         at org.apache.druid.java.util.common.guava.ParallelMergeCombiningSequence$SequenceBatcher.block(ParallelMergeCombiningSequence.java:920) [druid-core-0.20.0.jar:0.20.0]         at java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3313) [?:1.8.0_121]         at org.apache.druid.java.util.common.guava.ParallelMergeCombiningSequence$SequenceBatcher.getBatchYielder(ParallelMergeCombiningSequence.java:909) [druid-core-0.20.0.jar:0.20.0]         at org.apache.druid.java.util.common.guava.ParallelMergeCombiningSequence$YielderBatchedResultsCursor.initialize(ParallelMergeCombiningSequence.java:1017) [druid-core-0.20.0.jar:0.20.0]         at org.apache.druid.java.util.common.guava.ParallelMergeCombiningSequence$PrepareMergeCombineInputsAction.compute(ParallelMergeCombiningSequence.java:721) [druid-core-0.20.0.jar:0.20.0]         at java.util.concurrent.RecursiveAction.exec(RecursiveAction.java:189) [?:1.8.0_121]         at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) [?:1.8.0_121]         at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056) [?:1.8.0_121]         at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692) [?:1.8.0_121]         at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157) [?:1.8.0_121]

The exception stack reports an exception message saying No reachable node in cluster
Please use the redis command cluster info to check if the cluster is running OK

The exception stack reports an exception message saying No reachable node in cluster
Please use the redis command cluster info to check if the cluster is running OK

yes I did that and I see the clusters are running ok

yes I did that and I see the clusters are running ok

cluster info commands should outputs something like this

<IP_ADDRESS>:48003> cluster info
cluster_state:ok
cluster_slots_assigned:16384
cluster_slots_ok:16384
cluster_slots_pfail:0
cluster_slots_fail:0
cluster_known_nodes:6
cluster_size:3
cluster_current_epoch:6
cluster_my_epoch:3
cluster_stats_messages_ping_sent:72
cluster_stats_messages_pong_sent:75
cluster_stats_messages_sent:147
cluster_stats_messages_ping_received:75
cluster_stats_messages_pong_received:72
cluster_stats_messages_received:147

And could you tell me:

does this problem come out every time a query is being executed ?
what's the version of your redis server ?

cluster info commands should outputs something like this

<IP_ADDRESS>:48003> cluster info
cluster_state:ok
cluster_slots_assigned:16384
cluster_slots_ok:16384
cluster_slots_pfail:0
cluster_slots_fail:0
cluster_known_nodes:6
cluster_size:3
cluster_current_epoch:6
cluster_my_epoch:3
cluster_stats_messages_ping_sent:72
cluster_stats_messages_pong_sent:75
cluster_stats_messages_sent:147
cluster_stats_messages_ping_received:75
cluster_stats_messages_pong_received:72
cluster_stats_messages_received:147

And could you tell me:

does this problem come out every time a query is being executed ?
what's the version of your redis server ?

I am seeing this message now when I restart the broker.
2021-01-14T20:56:13,304 WARN [DruidSchema-Cache-0] org.apache.druid.client.cache.AbstractRedisCache - Exception pulling items from cache
redis.clients.jedis.exceptions.JedisClusterException: No way to dispatch this command to Redis Cluster because keys have different slots.
	at redis.clients.jedis.JedisClusterCommand.runBinary(JedisClusterCommand.java:75) ~[?:?]

I am seeing this message now when I restart the broker.
2021-01-14T20:56:13,304 WARN [DruidSchema-Cache-0] org.apache.druid.client.cache.AbstractRedisCache - Exception pulling items from cache
redis.clients.jedis.exceptions.JedisClusterException: No way to dispatch this command to Redis Cluster because keys have different slots.
	at redis.clients.jedis.JedisClusterCommand.runBinary(JedisClusterCommand.java:75) ~[?:?]

I don't see an error message every time when I run a query. (Since the Redis was not connected at startup itself)
Redis version : redis-cli 6.0.5

I don't see an error message every time when I run a query. (Since the Redis was not connected at startup itself)
Redis version : redis-cli 6.0.5

@FrankChen021 Any thoughts on this? Thanks for your time.

@FrankChen021 Any thoughts on this? Thanks for your time.

This error in historical node : ```
2021-01-14T20:56:13,647 WARN [segmentMetadata_dsp_media_and_bids_[2020-08-09T09:00:00.000Z/2020-08-09T10:00:00.000Z]] org.apache.druid.client.cache.AbstractRedisCache - Exception pulling item from cache
redis.clients.jedis.exceptions.JedisNoReachableClusterNodeException: No reachable node in cluster

This error in historical node : ```
2021-01-14T20:56:13,647 WARN [segmentMetadata_dsp_media_and_bids_[2020-08-09T09:00:00.000Z/2020-08-09T10:00:00.000Z]] org.apache.druid.client.cache.AbstractRedisCache - Exception pulling item from cache
redis.clients.jedis.exceptions.JedisNoReachableClusterNodeException: No reachable node in cluster

@FrankChen021 Any thoughts on this? Thanks for your time.

Based on my knowledge, I think this problem is more related to redis cluster itself and I have no idea what happened. It will take some time for me to investigate it. Thanks for your patience.

@FrankChen021 Any thoughts on this? Thanks for your time.

Based on my knowledge, I think this problem is more related to redis cluster itself and I have no idea what happened. It will take some time for me to investigate it. Thanks for your patience.

I am seeing this message now when I restart the broker. Broker log:
2021-01-14T20:56:13,304 WARN [DruidSchema-Cache-0] org.apache.druid.client.cache.AbstractRedisCache - Exception pulling items from cache
redis.clients.jedis.exceptions.JedisClusterException: No way to dispatch this command to Redis Cluster because keys have different slots.
	at redis.clients.jedis.JedisClusterCommand.runBinary(JedisClusterCommand.java:75) ~[?:?]

This is because there's a mget operation trying to get values with different keys distributed on different redis slots. Jedis does not support this kind of operation. Maybe in the future, we need to replace jedis with lettuce to eliminate this error.
And could you paste the full exception stack so that I could try to reproduce it when I have time to repair it ?

I am seeing this message now when I restart the broker. Broker log:
2021-01-14T20:56:13,304 WARN [DruidSchema-Cache-0] org.apache.druid.client.cache.AbstractRedisCache - Exception pulling items from cache
redis.clients.jedis.exceptions.JedisClusterException: No way to dispatch this command to Redis Cluster because keys have different slots.
	at redis.clients.jedis.JedisClusterCommand.runBinary(JedisClusterCommand.java:75) ~[?:?]

This is because there's a mget operation trying to get values with different keys distributed on different redis slots. Jedis does not support this kind of operation. Maybe in the future, we need to replace jedis with lettuce to eliminate this error.
And could you paste the full exception stack so that I could try to reproduce it when I have time to repair it ?

This error in historical node :
2021-01-14T20:56:13,647 WARN [segmentMetadata_dsp_media_and_bids_[2020-08-09T09:00:00.000Z/2020-08-09T10:00:00.000Z]] org.apache.druid.client.cache.AbstractRedisCache - Exception pulling item from cache
redis.clients.jedis.exceptions.JedisNoReachableClusterNodeException: No reachable node in cluster

For this problem, please check https://github.com/redis/jedis/issues/995
It provides two solutions for two problems:

enlarge the timeout configuration
or change bind-ip

This error in historical node :
2021-01-14T20:56:13,647 WARN [segmentMetadata_dsp_media_and_bids_[2020-08-09T09:00:00.000Z/2020-08-09T10:00:00.000Z]] org.apache.druid.client.cache.AbstractRedisCache - Exception pulling item from cache
redis.clients.jedis.exceptions.JedisNoReachableClusterNodeException: No reachable node in cluster

For this problem, please check https://github.com/redis/jedis/issues/995
It provides two solutions for two problems:

enlarge the timeout configuration
or change bind-ip

@FrankChen021

2021-01-15T22:06:13,611 WARN [DruidSchema-Cache-0] org.apache.druid.client.cache.AbstractRedisCache - Exception pulling items from cache
redis.clients.jedis.exceptions.JedisClusterException: No way to dispatch this command to Redis Cluster because keys have different slots.
	at redis.clients.jedis.JedisClusterCommand.runBinary(JedisClusterCommand.java:75) ~[?:?]
	at redis.clients.jedis.BinaryJedisCluster.mget(BinaryJedisCluster.java:1362) ~[?:?]
	at org.apache.druid.client.cache.RedisClusterCache.mgetFromRedis(RedisClusterCache.java:52) ~[?:?]
	at org.apache.druid.client.cache.AbstractRedisCache.getBulk(AbstractRedisCache.java:102) ~[?:?]
	at org.apache.druid.client.CachingClusteredClient$SpecificQueryRunnable.computeCachedValues(CachingClusteredClient.java:586) ~[druid-server-0.20.0.jar:0.20.0]
	at org.apache.druid.client.CachingClusteredClient$SpecificQueryRunnable.pruneSegmentsWithCachedResults(CachingClusteredClient.java:546) ~[druid-server-0.20.0.jar:0.20.0]
	at org.apache.druid.client.CachingClusteredClient$SpecificQueryRunnable.run(CachingClusteredClient.java:359) ~[druid-server-0.20.0.jar:0.20.0]
	at org.apache.druid.client.CachingClusteredClient.run(CachingClusteredClient.java:196) ~[druid-server-0.20.0.jar:0.20.0]
	at org.apache.druid.client.CachingClusteredClient.access$100(CachingClusteredClient.java:111) ~[druid-server-0.20.0.jar:0.20.0]
	at org.apache.druid.client.CachingClusteredClient$3.run(CachingClusteredClient.java:221) ~[druid-server-0.20.0.jar:0.20.0]
	at org.apache.druid.query.RetryQueryRunner.run(RetryQueryRunner.java:108) ~[druid-server-0.20.0.jar:0.20.0]
	at org.apache.druid.server.SetAndVerifyContextQueryRunner.run(SetAndVerifyContextQueryRunner.java:51) ~[druid-server-0.20.0.jar:0.20.0]
	at org.apache.druid.query.UnionQueryRunner.run(UnionQueryRunner.java:92) ~[druid-processing-0.20.0.jar:0.20.0]
	at org.apache.druid.query.metadata.SegmentMetadataQueryQueryToolChest$3.doRun(SegmentMetadataQueryQueryToolChest.java:124) ~[druid-processing-0.20.0.jar:0.20.0]
	at org.apache.druid.query.BySegmentSkippingQueryRunner.run(BySegmentSkippingQueryRunner.java:46) ~[druid-processing-0.20.0.jar:0.20.0]
	at org.apache.druid.query.FinalizeResultsQueryRunner.run(FinalizeResultsQueryRunner.java:110) ~[druid-processing-0.20.0.jar:0.20.0]
	at org.apache.druid.query.CPUTimeMetricQueryRunner.run(CPUTimeMetricQueryRunner.java:65) ~[druid-processing-0.20.0.jar:0.20.0]
	at org.apache.druid.query.ResultLevelCachingQueryRunner.run(ResultLevelCachingQueryRunner.java:96) ~[druid-server-0.20.0.jar:0.20.0]
	at org.apache.druid.query.FluentQueryRunnerBuilder$FluentQueryRunner.run(FluentQueryRunnerBuilder.java:55) ~[druid-processing-0.20.0.jar:0.20.0]
	at org.apache.druid.server.ClientQuerySegmentWalker$QuerySwappingQueryRunner.run(ClientQuerySegmentWalker.java:508) ~[druid-server-0.20.0.jar:0.20.0]
	at org.apache.druid.query.QueryPlus.run(QueryPlus.java:149) ~[druid-processing-0.20.0.jar:0.20.0]
	at org.apache.druid.server.QueryLifecycle.execute(QueryLifecycle.java:268) ~[druid-server-0.20.0.jar:0.20.0]
	at org.apache.druid.server.QueryLifecycle.runSimple(QueryLifecycle.java:142) ~[druid-server-0.20.0.jar:0.20.0]
	at org.apache.druid.sql.calcite.schema.DruidSchema.runSegmentMetadataQuery(DruidSchema.java:681) ~[druid-sql-0.20.0.jar:0.20.0]
	at org.apache.druid.sql.calcite.schema.DruidSchema.refreshSegmentsForDataSource(DruidSchema.java:532) ~[druid-sql-0.20.0.jar:0.20.0]
	at org.apache.druid.sql.calcite.schema.DruidSchema.refreshSegments(DruidSchema.java:494) ~[druid-sql-0.20.0.jar:0.20.0]
	at org.apache.druid.sql.calcite.schema.DruidSchema.lambda$start$2(DruidSchema.java:267) ~[druid-sql-0.20.0.jar:0.20.0]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_121]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_121]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_121]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_121]
	at java.lang.Thread.run(Thread.java:745) [?:1.8.0_121]

@FrankChen021

2021-01-15T22:06:13,611 WARN [DruidSchema-Cache-0] org.apache.druid.client.cache.AbstractRedisCache - Exception pulling items from cache
redis.clients.jedis.exceptions.JedisClusterException: No way to dispatch this command to Redis Cluster because keys have different slots.
	at redis.clients.jedis.JedisClusterCommand.runBinary(JedisClusterCommand.java:75) ~[?:?]
	at redis.clients.jedis.BinaryJedisCluster.mget(BinaryJedisCluster.java:1362) ~[?:?]
	at org.apache.druid.client.cache.RedisClusterCache.mgetFromRedis(RedisClusterCache.java:52) ~[?:?]
	at org.apache.druid.client.cache.AbstractRedisCache.getBulk(AbstractRedisCache.java:102) ~[?:?]
	at org.apache.druid.client.CachingClusteredClient$SpecificQueryRunnable.computeCachedValues(CachingClusteredClient.java:586) ~[druid-server-0.20.0.jar:0.20.0]
	at org.apache.druid.client.CachingClusteredClient$SpecificQueryRunnable.pruneSegmentsWithCachedResults(CachingClusteredClient.java:546) ~[druid-server-0.20.0.jar:0.20.0]
	at org.apache.druid.client.CachingClusteredClient$SpecificQueryRunnable.run(CachingClusteredClient.java:359) ~[druid-server-0.20.0.jar:0.20.0]
	at org.apache.druid.client.CachingClusteredClient.run(CachingClusteredClient.java:196) ~[druid-server-0.20.0.jar:0.20.0]
	at org.apache.druid.client.CachingClusteredClient.access$100(CachingClusteredClient.java:111) ~[druid-server-0.20.0.jar:0.20.0]
	at org.apache.druid.client.CachingClusteredClient$3.run(CachingClusteredClient.java:221) ~[druid-server-0.20.0.jar:0.20.0]
	at org.apache.druid.query.RetryQueryRunner.run(RetryQueryRunner.java:108) ~[druid-server-0.20.0.jar:0.20.0]
	at org.apache.druid.server.SetAndVerifyContextQueryRunner.run(SetAndVerifyContextQueryRunner.java:51) ~[druid-server-0.20.0.jar:0.20.0]
	at org.apache.druid.query.UnionQueryRunner.run(UnionQueryRunner.java:92) ~[druid-processing-0.20.0.jar:0.20.0]
	at org.apache.druid.query.metadata.SegmentMetadataQueryQueryToolChest$3.doRun(SegmentMetadataQueryQueryToolChest.java:124) ~[druid-processing-0.20.0.jar:0.20.0]
	at org.apache.druid.query.BySegmentSkippingQueryRunner.run(BySegmentSkippingQueryRunner.java:46) ~[druid-processing-0.20.0.jar:0.20.0]
	at org.apache.druid.query.FinalizeResultsQueryRunner.run(FinalizeResultsQueryRunner.java:110) ~[druid-processing-0.20.0.jar:0.20.0]
	at org.apache.druid.query.CPUTimeMetricQueryRunner.run(CPUTimeMetricQueryRunner.java:65) ~[druid-processing-0.20.0.jar:0.20.0]
	at org.apache.druid.query.ResultLevelCachingQueryRunner.run(ResultLevelCachingQueryRunner.java:96) ~[druid-server-0.20.0.jar:0.20.0]
	at org.apache.druid.query.FluentQueryRunnerBuilder$FluentQueryRunner.run(FluentQueryRunnerBuilder.java:55) ~[druid-processing-0.20.0.jar:0.20.0]
	at org.apache.druid.server.ClientQuerySegmentWalker$QuerySwappingQueryRunner.run(ClientQuerySegmentWalker.java:508) ~[druid-server-0.20.0.jar:0.20.0]
	at org.apache.druid.query.QueryPlus.run(QueryPlus.java:149) ~[druid-processing-0.20.0.jar:0.20.0]
	at org.apache.druid.server.QueryLifecycle.execute(QueryLifecycle.java:268) ~[druid-server-0.20.0.jar:0.20.0]
	at org.apache.druid.server.QueryLifecycle.runSimple(QueryLifecycle.java:142) ~[druid-server-0.20.0.jar:0.20.0]
	at org.apache.druid.sql.calcite.schema.DruidSchema.runSegmentMetadataQuery(DruidSchema.java:681) ~[druid-sql-0.20.0.jar:0.20.0]
	at org.apache.druid.sql.calcite.schema.DruidSchema.refreshSegmentsForDataSource(DruidSchema.java:532) ~[druid-sql-0.20.0.jar:0.20.0]
	at org.apache.druid.sql.calcite.schema.DruidSchema.refreshSegments(DruidSchema.java:494) ~[druid-sql-0.20.0.jar:0.20.0]
	at org.apache.druid.sql.calcite.schema.DruidSchema.lambda$start$2(DruidSchema.java:267) ~[druid-sql-0.20.0.jar:0.20.0]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_121]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_121]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_121]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_121]
	at java.lang.Thread.run(Thread.java:745) [?:1.8.0_121]

I tried a large timeout and also bind IP. still the same exception.

I tried a large timeout and also bind IP. still the same exception.

@FrankChen021 I tried a large timeout and was able to solve segment cache in historical.
But still getting the mget exception in broker.

Getting multiple values from different nodes by MGET are not supported by JEDIS now. I didn't notice this problem when I implemented redis cluster extension. We have to update the extension, either by calculating slots before such an operation or replacing jedis with lettuce.
I don't have a large chunk of time to do it these days, so I'm sorry that patch may not be shipped with 0.21 which is already on the way of release.

@FrankChen021 I tried a large timeout and was able to solve segment cache in historical.
But still getting the mget exception in broker.

Getting multiple values from different nodes by MGET are not supported by JEDIS now. I didn't notice this problem when I implemented redis cluster extension. We have to update the extension, either by calculating slots before such an operation or replacing jedis with lettuce.
I don't have a large chunk of time to do it these days, so I'm sorry that patch may not be shipped with 0.21 which is already on the way of release.


Query tab blank after SQL Server Connection

I can connect to my SQL Server db but when I switch to the Query tab, it is blank.

If I use the web interface (plot.ly/create) I can run a query and get the results.
I am on macOS Mojave 10.14.1 & Falcon 3.1.0

+1
Win 10 v1703, Falcon version 4.1

+1
This is frustrating :(
Win 10 v1809, Falcon version 4.1

+1
Win 10 v1703
I haven't been able to do anything in Falcon so far.

+1
Win 10 v18363

+1
Win 10 pro 20H2, Falcon version 4.1

+1
It still shows blank page and can not do anything except close the program and reopen it.


Update README.md

Add small hint on how to disconnect from tmux window.
Reason: as one who is not familiar with tmux intuitevely I tried to exit connected-mode with Crtl-C and got process killed :)

Useful info indeed. Thanks!


Resize images to requested size

The 256 × 256 images are a bit large if there are a lot on a page, and optimization analysis complains if you are only rendering them at 40x40, so allow resizing.

The fix looks good to me. Is that ready for merge?

Yes


fix: Grammatical errors in readme.md

Summary
Fixed some grammatical errors in readme.md

Changes Made

TODO

Motivation

Testing

Screenshots/GIFs

Checklist
Please ensure all of the following are completed before submitting the PR:

[x] Code has been tested and verified.
[x] Documentation has been updated to reflect the changes.
[x] All tests pass successfully.
[x] Code follows the project's coding guidelines and style.
[x] The branch is up-to-date with the latest changes from the main branch.
[x] Reviewed by at least one other contributor.

Related Issues
This PR addresses the following issue(s): []
Additional Notes

Thanks for your contribution, it's merged.

Enabling by hand since CLA will never return any status.


worksheets use relevant sbt file

Describe the feature
I open a worksheet inside of an existing scala project with an sbt file. I can import code from the project in the worksheet.
Potential ways to implement?
I'm not even sure why it doesn't work out of the box, don't know enough here
Additional context
n/a
Search terms
I think they're already here. Feel free to update this

Hello! So this actually works already, just maybe not the way you'd expect it to right away. So if the worksheet is contained next to the source in the build target, it will work and you'll be able to import from your file. If not, you won't have access to it. For example give a structure like this:
.
├── build.sbt
├── project
│  ├── build.properties
│  ├── plugins.sbt
│  └── src
│     └── main
│        ├── java
│        ├── scala
│        ├── scala-2
│        ├── scala-2.12
│        └── scala-sbt-1.0
└── src
   └── main
      └── scala
         ├── scala.worksheet.sc
         └── Example.scala

Inside of Example.scala
package example

object Example {
  val x = 3
}

You'll be able to access this in your worksheet:
example.Example.x
// x: Int = 3


Add a tutorial in readme file

illustrate how to write a model
how to run inference
how to summarize and visualise MCMC samples

I think we can extend&update the http://turingjl.readthedocs.io/getstarted.html#a-short-tutorial and put it in the README.md

Actually, we've already have 1 and 2. We introduced some new features (e.g. Mamba.Chains) in 0.2. We wan to illustrate these features, in particular describe(chain and plot(chain).


Import inheritance issue when using from()

Something strange is happening with imports, where they are not fully being inherited as expected when from() is used. I can zip up the files for easy repro but will summarize here.
I have a source defined in a file, mp_order_items.malloy:
source: order_items is table('malloy-data.ecomm.order_items')

I then import this into a second file, mp_middle.malloy where I introduce an additional source, users and define a query on top of order_items:
import "mp_order_items.malloy"

source: users is table('malloy-data.ecomm.users'){
  primary_key: id
}

source: test is from(order_items -> {project: *})

Finally, in a third file mp_ext.malloy I import mp_middle.malloy and run a query against the users source:
// import "mp_order_items.malloy"
import "mp_middle.malloy"

query: test_middle is users -> {
  group_by: id
}

This test_middle query will fail, with error Struct order_items not found in model.
If I uncomment import "mp_order_items.malloy" it works as expected.
If I don't use from in the middle file, for example just defining a source or query against order_items, everything works as expected even without the extra import.
Reported by @doit-mattporter

mp_import_bug_repro.zip
let me know if that zip doesn't work.

OK, the actual bug is that the bare import statement only imports sources not queries.
I think that's just wrong, and should be fixed, I'll wave it in front of people first just to make sure.
It should import sources and queries, but not SQL blocks, I believe.

nope i'm wrong about that ... i'm on it, more when i actually know things

Well this is super confusing ... why, when running "test_middle" does it even care about "order_items"

I know more things now.

I still don't know why, when parsing mp_ext the query in mp_middle is being loaded. That still seems weird and possibly broken, but maybe it isn't.

I understand why the load is failing. Imported things are not exported. Imported things are private. However we don't do the right thing when references to a private source or query are imported.


LINK : fatal error LNK1104: cannot open file 'box2d.lib'

Make sure these boxes are checked before submitting your issue - thank you!

[x] Ask for help on discord and/or reddit
[x] Consider providing a dump file using b2World::Dump

I've been trying to install and use the library for the last week and I've been unable to build a simple test program having the following error:
LINK : fatal error LNK1104: cannot open file 'box2d.lib' [D:\Documentos\UNIAT\Clases\Simulacion_fisicas2d\untitled\cmake-build-default-visual-studio\test.vcxproj]
I followed the CMake install guide with Program Files and then with in another location and the error keeps the same
FYI I'm using CLion 2023.1.5 with the following CMake Lists.txt:
cmake_minimum_required(VERSION 3.25)
project(test)

find_package(box2d CONFIG REQUIRED)

include_directories("D:/Documentos/UNIAT/packages")

set(CMAKE_CXX_STANDARD 17)

add_executable(test main.cpp)

target_link_libraries(test PRIVATE box2d)

and the following main code
#include <iostream>
#include "D:/Documentos/UNIAT/packages/include/box2d/box2d.h"
int main() {
    //Create the world
    b2Vec2 gravity(0.0f, -10.0f);
    b2World world(gravity);
    //Create the ground
    b2BodyDef groundBodyDef;
    groundBodyDef.position.Set(0.0f, -10.0f);
    b2Body* groundBody = world.CreateBody(&groundBodyDef);
    b2PolygonShape groundBox;
    groundBox.SetAsBox(50.0f, 10.0f);
    groundBody->CreateFixture(&groundBox, 0.0f);
    //Create the dynamic body
    b2BodyDef bodyDef;
    bodyDef.type = b2_dynamicBody;
    bodyDef.position.Set(0.0f, 4.0f);
    b2Body* body = world.CreateBody(&bodyDef);
    b2PolygonShape dynamicBox;
    dynamicBox.SetAsBox(1.0f, 1.0f);
    b2FixtureDef fixtureDef;
    fixtureDef.shape = &dynamicBox;
    fixtureDef.density = 1.0f;
    fixtureDef.friction = 0.3f;
    body->CreateFixture(&fixtureDef);
    //Simulate the world
    for (int32 i = 0; i < 60; ++i) {
        world.Step(1.0f / 60.0f, 6, 2);
        b2Vec2 position = body->GetPosition();
        float angle = body->GetAngle();
        std::cout << position.x << " " << position.y << " " << angle << std::endl;
    }
    return 0;
}

try linking to box2d::box2d instead of box2d

Thank you that was it


New Failure: py35.test.reflection._reflection_servicer_test.ReflectionServicerTest

Test: py35.test.reflection._reflection_servicer_test.ReflectionServicerTest
Poll Strategy: None
URL: https://kokoro2.corp.google.com/job/grpc/job/windows/job/master/job/grpc_basictests_dbg/114

This looks like an issue caused by a new google/protobuf release on PyPI. It was pushed yesterday (3.5.0)

Update: protobuf 3.5.1 is going to fix this issue. We have to wait till it gets published and this failure should go away.

Is there a timeline?
On 17 November 2017 at 14:32, Mehrdad Afshari<EMAIL_ADDRESS>wrote:

Update: protobuf 3.5.1 is going to fix this issue. We have to wait till it
gets published and this failure should go away.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/grpc/grpc/issues/13426#issuecomment-345383870, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAHVmZj5aXA52RcECKVlhfYdvC-pvrDsks5s3gmCgaJpZM4QhPlN
.

I heard it should be out before the next business week ends (i.e. Wednesday). I think the cause is diagnosed and the fix is going to be straightforward.

A supplementary update to 3.5.0 is uploaded to PyPI so this should be fixed now. Please ping the issue if you encounter it again for builds starting from now on.


2023-11-2 (02 Nov 2023) - Morphir Project Meeting

Date
Thursday 11/02/2023 - 3:30pm EST to 5pm EST
Untracked attendees

Name
Firm
Comment

Meeting notices

FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact<EMAIL_ADDRESS>with any questions.

FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[ ] Convene, roll call, welcome new people (5mins)
[ ] Display FINOS Antitrust Policy summary slide
[ ] Review Meeting Notices (see above)
[ ] Approve previous meeting minutes - https://github.com/finos/morphir/issues?q=is%3Aissue+is%3Aclosed+label%3Ameeting
[ ] Using Morphir to address regulatory cataloguing and lineage challenges
[ ] Gathering feedback on how we are now and can improve on "Going Beyond Business Rules with Morphir".
https://www.functionalscala.com/authors-and-speakers/damian-reeves
[ ] AOB, Q&A & Adjourn (5mins)

Decisions Made

[ ] Decision 1
[ ] Decision 2
[ ] ...

Action Items

[ ] Action 1
[ ] Action 2
[ ] ...

Meeting info
FINOS Morphir Project Meeting
We invite you to join us for this week's Morphir project meeting in person at the FINOS office, located at Rise.
Location: Rise Room 2.1
Date and Time: November 2nd, 3:30 pm - 5:00 pm EST
Zoom info

https://zoom.us/j/95452540437?pwd=TEk0bitJcVFsK3lrWVZCYmxyTm5LZz09
Meeting ID: 954 5254 0437
Passcode: 778814

Dial-in

Find your local number: https://zoom.us/u/aFGSSGV9x

Github Repo: https://github.com/finos/morphir/
Mailing List: Email<EMAIL_ADDRESS>to subscribe to our mailing list

Edward Peters @ Capital One

Damian Reeves/Capital One

James McLeod / FINOS

https://osr.finos.org/docs/welcome

Stephen Goldbaum @ Morgan Stanley


Feat/bump bq component version

What does this PR do?
Uses latest version of BQ component. This supports graceful handling of permissions.
Does your PR introduce any breaking changes? If yes, please list them.
No
Before submitting

[ ] Was this discussed/approved via a GitHub issue or with the team? (not for typos and docs)
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you list all the breaking changes introduced by this pull request?
[ ] Did you test your PR locally?
[ ] Did you test your PR on cloud?

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[ ] Make sure the title is self-explanatory and the description concisely explains the PR
[ ] Add labels to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃

hmm why is CI not happy?

hmm why is CI not happy?

because it's friday


Fix boilerplate-setup script for GNU find compatibility

📖 Description
The -depth has a different meaning in macOS (BSD) find than GNU find 🤦♂.
What we really want (that works in both ones) is -maxdepth.
📓 References
This should fix #338.
🦀 Dispatch

#dispatch/devops

🦀 Requesting reviewers for this pull request:

@Boubalou (contributor with 0 commits in the last 90 days and 11 commits overall)
@JoeyBG (reviewer for the devops stack)


AzDO CI is using GCC for Ubuntu.

This is something I noticed in one of our most recent logs, specifically in PR #54 . You can see the line here: https://dev.azure.com/NovelRT/NovelRT/_build/results?buildId=252&view=logs&j=3c3857a6-1d57-5b95-59be-23dc93fab9b7&t=b1a888d4-fc2f-5b54-84b8-f0547cafd7d8&l=40
I'm guessing this is just a flag we missed? It's supposed to register as Clang++.

The g++-8 usage here looks to be for the vcpkg build. The novelrt build is being done with clang

It looks like its because they explicitly override to use g++ here:https://github.com/microsoft/vcpkg/blob/master/scripts/bootstrap.sh#L200

Hmm, that's a bit weird. Do we just want to accept this as the default behaviour?
Is it possible clang might fall over at some point by mixing compilers like this?

Hmm, that's a bit weird.

Not really any more so than us referencing clang by default ;)

Do we just want to accept this as the default behaviour?

It looks like we might be able to override to clang, but I'd have to go through their build script more in depth to be sure.

Is it possible clang might fall over at some point by mixing compilers like this?

It shouldn't be a problem. We still build with clang like we intend to and clang and gcc are required to output binary compatible object files on Unix (which defines the elf file format, a standard calling convention and standard runtime abi).

Also, to maybe clarify, it looks like only the vcpkg executable that builds with gcc.
The "ports" (like sdl, nethost, freestyle, etc) are all built separately via cmake and look to use the system default (which we set to clang).

I see - yeah I guess us using clang is "non standard", though I'm choosing to use it to make our leap to mac easier. Though if you think its not an issue we could just leave it be if you think that's safest?

Yeah, I think leaving other repos using their preferred compiler is the safest choice; so I'll close this bug for now. We would likely need to open a bug against vcpkg to support clang by default if we wanted something else.


⚠ GitLab Server has degraded performance

In 4493cae, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 500
Response time: 16482 ms

Resolved: GitLab Server performance has improved in c6bbcb3.


Hot-module-replacement bubbling

Is your feature request related to a problem? Please describe.
My feature request is related to Prefresh this enables fast-refresh for Preact.
We handle the hot-reloading of custom-hooks slightly different, instead of giving a custom-hook the hot.accept callback we rely on HMR bubbling this allows us to refresh the dependent components and compare the signatures of the full hooks-stack to determine if state can be kept or not.
A scenario, imagine we have a useCounter.js and a Counter.js component, when we update useCounter it will bubble up to Counter, now this component can decide whether or not it has to dispose all state, if it does have to dispose the state we can still just rerender with an update reference to useCounter instead of having to force a location.reload().
useCounter has explicitly bubbled up, marking it as in need of an update, this allows us to bubble up to Counter, this components re-requests itself, we see that it is importing a module in need of an update (useCounter in this case) and we rebuild the file.
I think this will also be needed for full custom-hook support in React fast-refresh.
Describe the solution you'd like
I've recently implemented this in snowpack and like how we solved it there, we define clear boundaries, these boundaries are hot.accept calls, when these are present we can stop bubbling but when a module doesn't have one we check if dependent modules are accepting HMR-signals and mark that module as in need of an update.
When we reach the end of a tree without accept calls we resort back to location.reload()
Additional context
This behavior is in line with how HMR behaves in traditional bundler setups.

There is bubbling, I think there's some issue to be sorted out on how a self-accepting module is supposed to update. Let's track in https://github.com/vuejs/vite/issues/197


Increase journald retention period of some logs

How long are logs stored in journalctld?
It would be nice to be able to increase the retention for some types of logs. I do not know if this is even possible or if it's an all or nothing setting.

Currently journals are not saved, they are only stored in memory.

# journalctl --list-boots
 0 id0 Wed 2016-08-24 08:30:21 EEST—Wed 2016-08-24 09:18:32 EEST

mkdir /var/log/journal
rebooted (still only one)
another reboot (now it has two)

# journalctl --list-boots
-1 id1 Wed 2016-08-24 09:21:11 EEST—Wed 2016-08-24 09:23:41 EEST
 0 id2 Wed 2016-08-24 09:25:30 EEST—Wed 2016-08-24 09:26:35 EEST

Looking at https://github.com/CSC-IT-Center-for-Science/ansible-systemd-journal to create that directory.

Using that since f7982a7f9391b4241b56f50a6c37a2221813ba94


Run integration tests in GitHub Actions

The next release, 1.3.0, is expected to include a new test suite for the tracker, integration tests. These tests use Snowplow Micro, to send some events and retrieve the validation results per Micro API specs.
The under-development test suite can be run as expected locally while running them in Travis may end up failed. Sometimes they work as expected and I suspect this is because we didn't fix the emulator launched inside Travis. We need to fix this issue with running ui tests in Travis environment. Until then, we'll run ui tests by hand locally during development.

As you have pointed out having code that is running inside of the android app (AndroidJunitTest) to communicate to the local server running outside of the android on host system (snowplow micro) is a major headache.
Things I noticed, while trying to make this integration:

Discoverability. localhost inside of the android resolves to different address, so there is a requirement to use external service from outside network
Docker daemon requirement. To start snowplow micro docker daemon is needed, which not every cloud/ci provider easily gets access to due to exposing vulnerabilities. Check https://github.com/GoogleContainerTools/kaniko for more info
More importantly, docker daemon requirement means, that we can't control, start/stop snowplow micro from the test itself. Meaning, snowplow micro becomes a static resource, with all of the downsides of having static state in tests -> each test has to additionally validate/clear state, tests can't be run in parallel

Was it considered to restructure test approach to either:

Make snowplow micro running in android jvm. So, similarly, to https://github.com/square/okhttp/tree/master/mockwebserver it would be possible to have everything running inside of the android and control it from android junit instrumentation test
Or vice versa, remove hard dependency of android snowplow sdk on android by making it pluggable. We can manage snow-plow-micro on jvm unit tests with https://github.com/testcontainers/testcontainers-java . But after that snowplow-android-tracker is not ready to ignore missing AdvertisementID and so on, even with robolectric (android runtime on jvm)

Hi @plastiv , thanks for the detailed comment. Your observations are correct. We can always question and reconsider our approaches including how we test.
My opinions on your recommendations are below.
The reason Micro has an HTTP interface is to enable more usage scenarios compared to targeting only one platform, apart from other snowplow ecosystem related reasons. There might be a future version of Micro supporting gRPC communication to handle Micro operations directly in JVM but server would stay there at the end of the day, i.e. no parallel testing in that case too
I checked testcontainers project and it seems useful but Travis CI offers docker support and I'm not sure if it is worth the effort to switch how we change docker container. I couldn't see how it'll improve our process.
I think that no matter how we launch/run Micro, as long as we have one Micro instance running, we won't run tests in parallel. In case we consider launching multiple Micro instances, we can do that in the current setup too.
Please let me know if I'm missing anything.

Closing since we don't have Micro tests implemented currently – that will be the next action in this regard but we should have a separate issue for it.


Added IP scan by range and updated phpunit

also I've bumped the required php version to 5.6 (need to update travis.yml) but i don't know if you want to make this change or keep the old compatibility. Then phpunit can be downgraded to 3.7 again.

did not know this nmap feature, I’m going to close this PR 😉 Thanks!


pkgsStatic: Don't disable static on curl for git

Motivation for this change
Makes static git build.
Things done

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

Built on platform(s)

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"

[ ] Tested execution of all binary files (usually in ./result/bin/)

[ ] Determined the impact on package closure size (by running nix path-info -S before and after)

[ ] Ensured that relevant documentation is up to date

[x] Fits CONTRIBUTING.md.

[x] tested via static-haskell-nix

Notify maintainers
cc @matthewbauer

Doesn't makeStaticLibraries do this automatically?

Yes, same confusion as in #66417, closing.


proposal: core dump reader

I propose to develop a set of packages to enable the reading of core dumps generated by Go programs.
This set of packages will enable writing tools which can perform post-mortems on crashing Go servers.  An example might be out-of-memory analysis: looking for how many allocated objects of each type they are, why they are considered live, etc.
This proposal is particularly about the library that can read core dumps. The actual tools based on this library are a separate proposal.
I propose to add these packages somewhere in x/tools.
I've written up a small design doc with more details.

x/tools is fine (even without resolving exactly what x/tools is for, it's close enough to this).
Will leave design details to others, but as far as I'm concerned you can approve this whenever.
/cc @aclements @dr2chase @heschik @RLH

Going to mark this accepted to move out of the proposal queue. I assume you know the right people to discuss the design with.

This now exists: golang.org/x/debug/cmd/viewcore (+ internal helpers).
Closing.

Unless I'm mistaken, @randall77, that does not resolve the original issue. This issue is about the packages, not the tooling.

This proposal is particularly about the library that can read core dumps. The actual tools based on this library are a separate proposal.
I propose to add these packages somewhere in x/tools.

More specifically, I'm seeing that the packages used by viewcore are internal only.
https://github.com/golang/debug/blob/547453c34fb121ed0dae9624edc8a7a0c1e4e87d/cmd/viewcore/main.go#L24-L25

@lrstanley True. I argued for external, but was convinced otherwise by the folks who were actually going to maintain the tool.
You can always fork those libraries if you'd like to use them.


[IRGen] Check if type is empty instead of void in CallEmission::emitT…

…oUnmappedExplosionWithDirectTypedError
rdar://140573912
This caused assertions to fail when using other empty types, like Never as the result type on typed throwing functions.

@swift-ci smoke test

@swift-ci smoke test


Notification receive in but just hide in status bar.

Hi guys, thanks for contributing this great library, it is easy and nice to use. But I do have some question to ask.
Now my situation is I do try set priority setting to high/max/1 in android

When Apps in background,

receive notification, no flip out in the screen, it just hide in status bar, but got sound.
user tap
trigger onNotificationOpen(), show receive in background
When

Apps in foreground, receive notification

nothing from notification, no flip out, no in the status bar, but trigger onNotificationOpen()  showreceive in foreground

My question is, is that a right way to deal with android notification? Because it seem like scenario 1 should be show in flip/expanded notification no matter in any place of android right? While I do appreciate the call back is wrong but when there is no flip out, user doesn't know there is urgent right?
Then come the scenario 2, apps also still need show flip even when user is using the apps right? so that user know there is urgent to do some action. If there is only a call back being trigger, what should I do next?
I no very familiar with android notification setting/UX, anyone has suggestion?

I've the same problem, have anyone some fix?

closing for now, reopen if still an issue with the latest version of the plugin


Refractor to use a single Selenium instance #28

I haven't been able to test this code because I don't even play WoW, but I have been working with Selenium and this is a very similar issue that I have been able to implement successfully in the past.
Key changes include:

Selenium instance management: The start_browsers() function has been added to initialize the headless and visible Selenium browser instances at the start of the script execution. Similarly, the close_browsers() function has been added to close these instances at the end of the script execution.

Global usage of Selenium instances: All functions that use Selenium (get_cf_update_time, get_wago_update_time, get_wago_dl_url, dl_wago_addon, get_version_tuk_addon, download_tuk_addon) now use the global instances visible_browser and headless_browser instead of creating a new instance each time.

Removal of driver closure within functions: All lines that closed the Selenium instances (driver.close()) within individual functions have been removed, as the instances are meant to stay open for the duration of the script.

Please test the changes and change the code as needed to fit the specific details of your project.

Approved. Merging.
@RafaFuentesdev excellent work! I really appreciate the contribution. :)

Thanks for the kind words! I'm always happy to help out. Keep up the great work yourself! @Lesona-Systems


Version Numbers

Would it be possible to include the version numbers in the filenames for the releases? Cheers.

Good point, I will do that for the next release.


Roles for read only

Global reader is not listed as a role that can read the preset policies, is that an oversite, or is that role really not eligible to see these items?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4f6f1cf3-a121-3c6e-9380-79440f4c6671
Version Independent ID: 9b1bc5d1-8ecc-d0f9-092e-325c6acff4fe
Content: Preset security policies - Office 365
Content Source: microsoft-365/security/office-365-security/preset-security-policies.md
Service: o365-seccomp
GitHub Login: @chrisda
Microsoft Alias: chrisda

@DeanGross Global reader is eligible to see these items. I have added it to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/3318
Thanks
Sri

@msbemba Thank you very much for the contribution and updating the documentation with PR. @DeanGross Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Server error<EMAIL_ADDRESS>

Cannot find module 'brfs' from '/var/app/current/.tmp/0d81e35f1ec28eb19114afd9473a49b7a29d9318/package'

See<EMAIL_ADDRESS>

Looks like a problem with the package itself:
https://github.com/RThevenoux/ipa-parser/pull/1


feat: Allow inherits_from behavior between Meltano environments.

This would allow meltano environments to be declared more sparsely.
For instance, a userdev environment might be fully unique and declared independently, while a staging or uat environment would inherit from prod with just the bare minimum number of overrides to ensure isolation of Meltano-created resources.

Still relevant


chore: remove litecoin feature flag

Description

remove LTC feature flag
Notice

[x] Have you followed the guidelines in our Contributing guide?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[x] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

n/a
Risk

litecoin disappears, or doesn't work correctly with keepkey.
Testing

ensure litecoin still appears with demo wallet and works with keepkey
Screenshots (if applicable)

Current dependencies on/for this PR:

develop

PR #2505

PR #2506   👈

PR #2507

This comment was auto-generated by Graphite.


mistake in textual definition of microbiology data terms

Children of 'organism identification datum' are textually defined as types of assay rather than types of data. This PR corrects that.

I will merge this and make a new release. Since we had lots of time to review #1631, I will not bother with another release candidate -- I will just release.


Add a ScopeNode and a way to create scope nodes from existing nodes

This commit creates a scope node, and exposes a method to get ScopeNodes from other existing nodes. It still has TODOs around creating ScopeNodes for other types of nodes, which will be done in future commits.

What's the purpose of it? Isn't it enough to use the fields of DefNode, etc directly?
Or is the idea to move constant[] locals to a ScopeNode and have DefNode have a ScopeNode field?
That seems potentially problematic for BlockNode which has a BlockParametersNode and not a ParametersNode.

Is it maybe just a helper for C code using YARP?
If so it feels like ScopeNode shouldn't exist in Ruby & Java then, since it's never really part of the AST returned by YARP.parse.
I think it should be its own manually declared struct then and not end with node since it's not a node.

Is it maybe just a helper for C code using YARP?

It seems so: https://github.com/ruby/yarp/pull/1307/files#diff-0fde49ffd5b93b6e12016a9869a7ddccaf881a68e979c5a90bf99c89836df604R38-R40
It would be nice if such fundamental questions about the PR is answered and maybe the description improved, it would be much clearer what the PR is about.


dotnet nuget push "SkipDuplicate" option for org feed

Required Information
Type: Feature
Enter Task Name: DotNetCoreCLI
Issue Description
When using the DotNetCoreCLI task, command "nuget push", it is not possible to specify "SkipDuplicates". This option does seem to exist on the cli itself and in the Nuget task.

In YAML terms:
steps:
- task: DotNetCoreCLI@2
  displayName: 'dotnet push'
  inputs:
    command: push
    packagesToPush: '$(System.DefaultWorkingDirectory)/_testpackage/drop/**/*.nupkg'
    publishVstsFeed: 'testfeedguid'

- task: NuGetCommand@2
  displayName: 'NuGet push'
  inputs:
    command: push
    publishVstsFeed: 'testfeedguid'
    allowPackageConflicts: true

@bishal-pdMSFT @pulkitaggarwl Shall we add this to our backlog?

Gently /ping on this issue @vineetmimrot @bishal-pdMSFT @pulkitaggarwl @damccorm . Happy to submit a PR if that helps.

The PR is open, I'm happy to suggest the change in the documentation once and if it gets merged and deployed. Thank you.

I have discussed this with the team and we have decided not to add this functionality to the task. Instead of using these "bulkier" tasks we now recommend using the NuGet Authenticate task to authenticate to Azure DevOps Artifacts feeds and to use a script task with nuget/dotnet to use the parameters you need.
- task: NuGetAuthenticate@0
- task: UseDotNet@2 # Optional if the .NET Core SDK is already installed
- script: dotnet restore
# ...
- script: dotnet nuget push --api-key AzureArtifacts --skip-duplicate --source https://pkgs.dev.azure.com/{organization}/{project?}/_packaging/{feed1}/nuget/v3/index.json MyProject.*.nupkg

The reason for this is that the NuGet/Dotnet clients are actively being developed and new parameters and functionality are being added often. To keep up with all of the updates causes a lot of extra support for these bulky tasks. Please use example above to set up your pipeline with the '--skip-duplicate' parameter. Thank you for understanding.

Thanks for the feedback.
Seems this means we should abandon any tasks all together and go back to scripting...

For anyone using Azure DevOps Server (on-prem):
The workaround suggested above does not work with ADO Server, as the NuGet Authenticate task is not available in ADO Server.
It appears that there is a method to manually add the task, but as far as I can tell, the task isn't included in any "official" ADO Server release.

For those of you that arrived here looking for an answer, the official Microsoft documentation for NuGet Authenticate helped me to implement 'SkipDuplicates' in my Azure DevOps-hosted YAML pipeline:
`
steps:

task: DotNetCoreCLI@2
displayName: Build
inputs:
command: 'build'
projects: '**/*.csproj'
task: DotNetCoreCLI@2
displayName: Pack
inputs:
command: 'pack'
packagesToPack: '**/*.csproj'
nobuild: true
versioningScheme: 'off'
task: NuGetAuthenticate@0
displayName: Authenticate to Local NuGet feed(s)
script: dotnet nuget push --source "https://pkgs.dev.azure.com/{my-organization}/{my-project}/_packaging/{my-package-source}/nuget/v3/index.json" --api-key az --skip-duplicate **/*.nupkg
`

TFS is basically abandonware at this point.  I would advice potential users to look at better options from Atlassian, who actually support their products.


StaticRoute is broken in 0.16.0

Hi. In commit d6f4764bb3e070afcd42893657518150242f0d41 you removed limit variable from the StaticRoute class, but that variable is still used over here. Because of this, StaticRoute does not work in 0.16.0 release; it throws this error:
...
    chunk = f.read(self.limit)
AttributeError: 'StaticRoute' object has no attribute 'limit'

Fixed in release 0.16.1
Thanks for report!


Updated inline playback tag for iOS 10.

This should fix #160

can you make this update available on bower?

@rremy It doesn't work for me, neither does it do on the videogular demo :(

Thanks for the change.
regarding this ios update:
[(https://webkit.org/blog/6784/new-video-policies-for-ios/)]
This should be working fine.


How to disable ha zk?

1. Describe the bug
How to disable ha zk? I set kyuubi.ha.enabled=false, but not working

2. Environments
2.1 Versions

Kyuubi

[ ] 1.1.0
[ ] 1.0.3
[ ] 0.8.x and earlier

Spark

[ ] 3.1.x
[ ] 3.0.x
[ ] 2.4.x and earlier

2.2 Kyuubi Configurations
2.3 Spark Configurations
3. Steps to reproduce
3.1 Operations
3.2 Expected behavior

3.3 Actual behavior
4. Additional context
4.1 Log of the server
4.2 Log of the corresponding engine

Zookeeper (HA mode) is optional for Kyuubi Server but required for Engine.
When a new engine(spark driver) is launched, it will register itself in Zookeeper, then Kyuubi Server knows how to connect to the engine.

@pan3793 Ok, thx


More custom assembly updates.

Seeing as custom assembly code doesn't automatically exclude editor classes, and we need to define our own, I renamed the editor folder to inspectors.
Also fixed some issues with standalone compilation.
Ported over settings enforcement script and updated it to use .net standard 2, but not complain if users target the broader .net 4.x runtime.

I'll not merge this one until you say you're ready this time @StephenHodgson  :D


getting error in ekf

I'm not using depth sensor.
[ekf_node-2] Warning: Invalid frame ID "base_footprint" passed to canTransform argument target_frame - frame does not exist [ekf_node-2]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.12/src/buffer_core.cpp [ekf_node-2] Warning: Invalid frame ID "base_footprint" passed to canTransform argument target_frame - frame does not exist [ekf_node-2]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.12/src/buffer_core.cpp [ekf_node-2] Warning: Invalid frame ID "imu_link" passed to canTransform argument source_frame - frame does not exist [ekf_node-2]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.12/src/buffer_core.cpp [ekf_node-2] Warning: Invalid frame ID "imu_link" passed to canTransform argument source_frame - frame does not exist [ekf_node-2]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.12/src/buffer_core.cpp [ekf_node-2] Warning: Invalid frame ID "imu_link" passed to canTransform argument source_frame - frame does not exist [ekf_node-2]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.12/src/buffer_core.cpp [ekf_node-2] Warning: Invalid frame ID "imu_link" passed to canTransform argument source_frame - frame does not exist [ekf_node-2]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.12/src/buffer_core.cpp

I need more information about your system. Could you tell me what's your setup like? Robot base, imu, microcontroller, operating system, ROS distro?

robot base : 4wd
imu : 9250
microcontroller : raspberry pi4
operating system : ubuntu20.04.3 (Focal Fossa)
ros : ros2 foxy fitzroy
and I'm not using depth sensor I didn't mention depth sensor while installation is it need to edit workspace or urdf file.

are you getting anything when you echo the following topics?
/imu/data
/odom/unfiltered

yes

which launch file does this happen?

bringup file

can you post your rqt_graph here?

sorry man I can't able to get rqt_graph
it doesn't work properly in ros2

everything works fine except efk
also able to move bot using teleop keyboard.
error I'm facing is
`ubuntu@uvbot:~/linorobot2_ws$ ros2 launch linorobot2_bringup bringup.launch.py
[INFO] [launch]: All log files can be found below /home/ubuntu/.ros/log/2021-11-14-08-47-00-703236-uvbot-3828
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [ydlidar_ros2_driver_node-5]: process started with pid [3857]
[INFO] [micro_ros_agent-1]: process started with pid [3849]
[INFO] [ekf_node-2]: process started with pid [3851]
[INFO] [joint_state_publisher-3]: process started with pid [3853]
[INFO] [robot_state_publisher-4]: process started with pid [3855]
[micro_ros_agent-1] [1636879622.171197] info     | TermiosAgentLinux.cpp | init                     | running...             | fd: 3
[micro_ros_agent-1] [1636879622.172139] info     | Root.cpp           | set_verbose_level        | logger setup           | verbose_level: 4
[micro_ros_agent-1] [1636879622.186130] info     | Root.cpp           | create_client            | create                 | client_key: 0x7C881CDA, session_id: 0x81
[micro_ros_agent-1] [1636879622.186261] info     | SessionManager.hpp | establish_session        | session established    | client_key: 0x7C881CDA, address: 0
[micro_ros_agent-1] [1636879622.266785] info     | ProxyClient.cpp    | create_participant       | participant created    | client_key: 0x7C881CDA, participant_id: 0x000(1)
[micro_ros_agent-1] [1636879622.267979] info     | ProxyClient.cpp    | create_topic             | topic created          | client_key: 0x7C881CDA, topic_id: 0x000(2), participant_id: 0x000(1)
[micro_ros_agent-1] [1636879622.270327] info     | ProxyClient.cpp    | create_publisher         | publisher created      | client_key: 0x7C881CDA, publisher_id: 0x000(3), participant_id: 0x000(1)
[micro_ros_agent-1] [1636879622.276638] info     | ProxyClient.cpp    | create_datawriter        | datawriter created     | client_key: 0x7C881CDA, datawriter_id: 0x000(5), publisher_id: 0x000(3)
[micro_ros_agent-1] [1636879622.278927] info     | ProxyClient.cpp    | create_topic             | topic created          | client_key: 0x7C881CDA, topic_id: 0x001(2), participant_id: 0x000(1)
[micro_ros_agent-1] [1636879622.281726] info     | ProxyClient.cpp    | create_publisher         | publisher created      | client_key: 0x7C881CDA, publisher_id: 0x001(3), participant_id: 0x000(1)
[micro_ros_agent-1] [1636879622.284666] info     | ProxyClient.cpp    | create_datawriter        | datawriter created     | client_key: 0x7C881CDA, datawriter_id: 0x001(5), publisher_id: 0x001(3)
[micro_ros_agent-1] [1636879622.287036] info     | ProxyClient.cpp    | create_topic             | topic created          | client_key: 0x7C881CDA, topic_id: 0x002(2), participant_id: 0x000(1)
[micro_ros_agent-1] [1636879622.288837] info     | ProxyClient.cpp    | create_subscriber        | subscriber created     | client_key: 0x7C881CDA, subscriber_id: 0x000(4), participant_id: 0x000(1)
[micro_ros_agent-1] [1636879622.296376] info     | ProxyClient.cpp    | create_datareader        | datareader created     | client_key: 0x7C881CDA, datareader_id: 0x000(6), subscriber_id: 0x000(4)
[ydlidar_ros2_driver_node-5] [INFO] [1636879622.330339628] [ydlidar_ros2_driver_node]: [YDLIDAR INFO] Current ROS Driver Version: 1.0.1
[ydlidar_ros2_driver_node-5]
[ydlidar_ros2_driver_node-5] YDLidar SDK initializing
[ydlidar_ros2_driver_node-5] YDLidar SDK has been initialized
[ydlidar_ros2_driver_node-5] [YDLIDAR]:SDK Version: 1.0.3
[robot_state_publisher-4] Parsing robot urdf xml string.
[robot_state_publisher-4] Link base_link had 7 children
[robot_state_publisher-4] Link camera_link had 1 children
[robot_state_publisher-4] Link camera_depth_link had 0 children
[robot_state_publisher-4] Link front_left_wheel_link had 0 children
[robot_state_publisher-4] Link front_right_wheel_link had 0 children
[robot_state_publisher-4] Link imu_link had 0 children
[robot_state_publisher-4] Link laser had 0 children
[robot_state_publisher-4] Link rear_left_wheel_link had 0 children
[robot_state_publisher-4] Link rear_right_wheel_link had 0 children
[robot_state_publisher-4] [INFO] [1636879622.409395700] [robot_state_publisher]: got segment base_footprint
[robot_state_publisher-4] [INFO] [1636879622.409787774] [robot_state_publisher]: got segment base_link
[robot_state_publisher-4] [INFO] [1636879622.409879570] [robot_state_publisher]: got segment camera_depth_link
[robot_state_publisher-4] [INFO] [1636879622.409915903] [robot_state_publisher]: got segment camera_link
[robot_state_publisher-4] [INFO] [1636879622.409944107] [robot_state_publisher]: got segment front_left_wheel_link
[robot_state_publisher-4] [INFO] [1636879622.409971903] [robot_state_publisher]: got segment front_right_wheel_link
[robot_state_publisher-4] [INFO] [1636879622.409999181] [robot_state_publisher]: got segment imu_link
[robot_state_publisher-4] [INFO] [1636879622.410025106] [robot_state_publisher]: got segment laser
[robot_state_publisher-4] [INFO] [1636879622.410052477] [robot_state_publisher]: got segment rear_left_wheel_link
[robot_state_publisher-4] [INFO] [1636879622.410079606] [robot_state_publisher]: got segment rear_right_wheel_link
[ydlidar_ros2_driver_node-5] LiDAR successfully connected
[ekf_node-2] Warning: Invalid frame ID "base_footprint" passed to canTransform argument target_frame - frame does not exist
[ekf_node-2]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.12/src/buffer_core.cpp
[ekf_node-2] Warning: Invalid frame ID "base_footprint" passed to canTransform argument target_frame - frame does not exist
[ekf_node-2]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.12/src/buffer_core.cpp
[ekf_node-2] Warning: Invalid frame ID "base_footprint" passed to canTransform argument target_frame - frame does not exist
[ekf_node-2]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.12/src/buffer_core.cpp
[ekf_node-2] Warning: Invalid frame ID "base_footprint" passed to canTransform argument target_frame - frame does not exist
[ekf_node-2]          at line 133 in /tmp/binarydeb/ros-foxy-tf2-0.13.12/src/buffer_core.cpp
[ydlidar_ros2_driver_node-5] [YDLIDAR]:Lidar running correctly !  Or does it stop? If it stops, that warning shows up right before the imu/odometry is published. If you launch the slam launch file, do you have the same error?

no the warning from the efk stops.
but in slam launch file continue - the error shown in ros2 launch linorobot2_navigation slam.launch.py
is continuously shown.
[async_slam_toolbox_node-1] [INFO] [1636882967.764174681] [slam_toolbox]: Message Filter dropping message: frame 'laser' at time<PHONE_NUMBER>.536 for reason 'Unknown' [async_slam_toolbox_node-1] [INFO] [1636882967.877698649] [slam_toolbox]: Message Filter dropping message: frame 'laser' at time<PHONE_NUMBER>.650 for reason 'Unknown' [async_slam_toolbox_node-1] [INFO] [1636882968.275302731] [slam_toolbox]: Message Filter dropping message: frame 'laser' at time<PHONE_NUMBER>.764 for reason 'Unknown' [async_slam_toolbox_node-1] [INFO] [1636882968.275689398] [slam_toolbox]: Message Filter dropping message: frame 'laser' at time<PHONE_NUMBER>.878 for reason 'Unknown'

does it stop as well? Are you able to create a map?

nope

as in a complete map?

no i cant able to move the base_footprint robot model in the rviz doesn't move.
u can see only odom node is moving.

could you try adding these https://github.com/cra-ros-pkg/robot_localization/blob/ros2/params/ekf.yaml#L23-L27 to this https://github.com/linorobot/linorobot2/blob/master/linorobot2_base/config/ekf.yaml . 0.1 would be a good start

thankyou so much grassjelly now the ekf error gone.
the robot model in the rviz doesn't move.
the map looks uneven i think its something to do with laser pose urdf file.

Great! Could you please share your updated ekf.yaml here? Would be useful for other users. Please file another issue if you’re having problems with mapping. Thanks

updated ekf.yaml
`ekf_filter_node:
ros__parameters:
frequency: 50.0
two_d_mode: true
publish_tf: true
    map_frame: map
    odom_frame: odom
    base_link_frame: base_footprint
    world_frame: odom
	transform_time_offset: 0.1
    transform_timeout: 0.1

    #x     , y     , z,
    #roll  , pitch , yaw,
    #vx    , vy    , vz,
    #vroll , vpitch, vyaw,
    #ax    , ay    , az
    odom0: odom/unfiltered
    odom0_config: [false, false, false,
                   false, false, false,
                   true, true, false,
                   false, false, true,
                   false, false, false]

    imu0: imu/data
    imu0_config: [false, false, false,
                  false, false, false,
                  false, false, false,
                  false, false, true,
                  false, false, false]`


block device backing zpool on lvm isn't detected properly

Setting limits.read, limits.write for a container :
# lxc config show ct04
name: ct04
profiles:
- small
config:
  boot.autostart: "false"
  user.ens.p: "1"
  user.ens.x: "12.2"
  volatile.base_image: 4525094c3dd2c58b0a60feac5e72963942062ea74f2ee08bcba13a7b448712e4
  volatile.eth0.hwaddr: 00:16:3e:3c:e8:b0
  volatile.eth0.name: eth0
  volatile.last_state.idmap: '[{"Isuid":true,"Isgid":false,"Hostid":165536,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":165536,"Nsid":0,"Maprange":65536}]'
  volatile.lo.hwaddr: 00:16:3e:02:26:b5
  volatile.lo.name: eth1
devices:
  eth0:
    host_name: vlan100ct04
    nictype: bridged
    parent: vlan100
    type: nic
  root:
    limits.read: 100kB
    limits.write: 100kB
    path: /
    type: disk

does (from log):
lxc<PHONE_NUMBER>4116.069 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1960 - cgroup 'blkio.throttle.read_bps_device' set to '252:0 102400'
lxc<PHONE_NUMBER>4116.069 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1960 - cgroup 'blkio.throttle.write_bps_device' set to '252:0 102400'
lxc<PHONE_NUMBER>4116.069 INFO     lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1964 - cgroup has been setup

but dev 252:0 is just a :
# ls -l /dev |grep 252
brw-rw---- 1 root   disk    252,   0 Feb 26 08:02 dm-0
brw-rw---- 1 root   disk    252,   1 Feb 26 08:02 dm-1
brw-rw---- 1 root   disk    252,   2 Feb 26 08:02 dm-2
root@ubuntu:/dev# dmsetup ls
ubuntu--vg-lxd  (252:2)
ubuntu--vg-swap_1       (252:1)
ubuntu--vg-root (252:0)
root@ubuntu:/dev# lvs
  LV     VG        Attr       LSize  Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  lxd    ubuntu-vg -wi-ao---- 50.00g (not used - not mounted)
  root   ubuntu-vg -wi-ao---- 33.25g
  swap_1 ubuntu-vg -wi-ao----  4.00g
root@ubuntu:/dev# zpool list
NAME   SIZE  ALLOC   FREE  EXPANDSZ   FRAG    CAP  DEDUP  HEALTH  ALTROOT
lxd   49.8G  4.36G  45.4G         -    10%     8%  1.33x  ONLINE  -
root@ubuntu:/dev# mount |grep lxd
lxd on /lxd type zfs (rw,relatime,xattr,noacl)
lxd/containers on /lxd/containers type zfs (rw,relatime,xattr,noacl)
lxd/images on /lxd/images type zfs (rw,relatime,xattr,noacl)
lxd/containers/ct02-bugzilla on /var/lib/lxd/containers/ct02-bugzilla.zfs type zfs (rw,relatime,xattr,noacl)
lxd/containers/ct04 on /var/lib/lxd/containers/ct04.zfs type zfs (rw,relatime,xattr,noacl)
lxd/containers/ct05 on /var/lib/lxd/containers/ct05.zfs type zfs (rw,relatime,xattr,noacl)
lxd/containers/ctMySQL on /var/lib/lxd/containers/ctMySQL.zfs type zfs (rw,relatime,xattr,noacl)
lxd/containers/spid24-pl on /var/lib/lxd/containers/spid24-pl.zfs type zfs (rw,relatime,xattr,noacl)
lxd/images/4525094c3dd2c58b0a60feac5e72963942062ea74f2ee08bcba13a7b448712e4 on /var/lib/lxd/images/4525094c3dd2c58b0a60feac5e72963942062ea74f2ee08bcba13a7b448712e4.zfs type zfs (ro,relatime,xattr,noacl)
/dev/mapper/ubuntu--vg-root on /var/lib/lxd/shmounts type ext4 (rw,relatime,errors=remount-ro,data=ordered)

Limits are set on wrong device ... limiting is not working
I am not even sure if enforcing those limits is possible for separate CT's at ZFS without dedicated zvol for each?
Doc storage-backends.md is silent about lack of limits for zfs
Doc configuration.md also states that dev "Type: disk" has required "source" key - there is no such a key in automatically created CT's config
Did I miss come important README section?
Required information

Distribution: Ubuntu
Distribution version:15.10

#lxc info
apicompat: 0
auth: trusted
environment:
  addresses: []
  architectures:
  - x86_64
  - i686
  certificate: <cert>
  driver: lxc
  driverversion: 2.0.0.rc3
  kernel: Linux
  kernelarchitecture: x86_64
  kernelversion: 4.2.0-30-generic
  server: lxd
  serverpid: 17135
  serverversion: 2.0.0.beta4
  storage: zfs
  storageversion: "5"
config:
  storage.zfs_pool_name: lxd
public: false

Disk limits on zfs sort of work usually, I say sort of because zfs doesn't always use a kernel code path which supports them.
In your case it looks like your logic to find the block devices backing the zpool failed and went through a fallback mode that's usually only relevant to physical disk partitions.
It's not possible to set blkio limits on a partition, only on a full disk, so we have logic replacing the disk minor by 0 when it thinks the path is a partition, that's apparently failing on lvm.

Please post "zpool status -v"

# zpool status -v
  pool: lxd
 state: ONLINE
  scan: scrub repaired 0 in 0h2m with 0 errors on Wed Feb 24 10:16:49 2016
config:

        NAME              STATE     READ WRITE CKSUM
        lxd               ONLINE       0     0     0
          ubuntu--vg-lxd  ONLINE       0     0     0

errors: No known data errors
# lsblk
NAME                  MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
fd0                     2:0    1     4K  0 disk
sda                     8:0    0   127G  0 disk
├─sda1                  8:1    0   243M  0 part /boot
├─sda2                  8:2    0     1K  0 part
└─sda5                  8:5    0 126.8G  0 part
  ├─ubuntu--vg-root   252:0    0  33.3G  0 lvm  /
  ├─ubuntu--vg-swap_1 252:1    0     4G  0 lvm  [SWAP]
  └─ubuntu--vg-lxd    252:2    0    50G  0 lvm
sdb                     8:16   0    64G  0 disk
sr0                    11:0    1  1024M  0 rom
root@ubuntu:~# pvs
  PV         VG        Fmt  Attr PSize   PFree
  /dev/sda5  ubuntu-vg lvm2 a--  126.76g 39.51g

Ok, based on that output, my fix should work. It'll now look for /dev/mapper/ubuntu--vg-lxd which should exist on your system and then use that for the blkio quota.

This was was log from dev/test machine .. zfs at lvm is not very ... smart
I did sime test at other server I am preparing with sime result (also storage: zfs)  - below log - limit also do not work
root@frgra1:~# lxc config show ct100-03-dns
name: ct100-03-dns
profiles:

vlan100
small
config:
volatile.base_image: b03f56d3075a20e3ab84503d89dd71e6905c5360bb6e12b67049e700da1d83ef
volatile.eth0.hwaddr: 00:16:3e:62:79:bd
volatile.eth0.name: eth0
volatile.last_state.idmap: '[{"Isuid":true,"Isgid":false,"Hostid":165536,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":165536,"Nsid":0,"Maprange":65536}]'
volatile.lo.hwaddr: 00:16:3e:67:cc:9b
volatile.lo.name: eth1
devices:
eth0:
host_name: vlan100ct03
nictype: bridged
parent: vlan100
type: nic
root:
limits.read: 100kB
limits.write: 100kB
path: /
type: disk
ephemeral: false

#lxc restart ct100-03-dns
#lxc info ct100-03-dns --show-log|grep limits
lxc<PHONE_NUMBER>0624.729 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1960 - cgroup 'blkio.throttle.read_bps_device'        set to '252:0 102400'
lxc<PHONE_NUMBER>0624.729 DEBUG    lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1960 - cgroup 'blkio.throttle.write_bps_device'        set to '252:0 102400'
lxc<PHONE_NUMBER>0624.729 INFO     lxc_cgfs - cgfs.c:do_setup_cgroup_limits:1964 - cgroup has been setup
root@frgra1:~# zpool status -v
pool: lxd
state: ONLINE
scan: scrub repaired 0 in 0h0m with 0 errors on Thu Feb 25 13:45:46 2016
config:
    NAME                                                  STATE     READ WRITE CKSUM
    lxd                                                   ONLINE       0     0     0
      mirror-0                                            ONLINE       0     0     0
        ata-INTEL_SSDSC2BB480H4_BTWH5115021B480BGN-part3  ONLINE       0     0     0
        ata-INTEL_SSDSC2BB480H4_BTWH511503E8480BGN-part3  ONLINE       0     0     0

errors: No known data errors
ls -l /dev/disk/by-id/|grep part3
lrwxrwxrwx 1 root root 10 Feb 24 11:28 ata-INTEL_SSDSC2BB480H4_BTWH5115021B480BGN-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Feb 24 11:28 ata-INTEL_SSDSC2BB480H4_BTWH511503E8480BGN-part3 -> ../../sdb3
lsblk
NAME           MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda              8:0    0 447.1G  0 disk
├─sda1           8:1    0   243M  0 part
│ └─md0          9:0    0 242.8M  0 raid1 /boot
├─sda2           8:2    0    28G  0 part
│ └─md1          9:1    0  27.9G  0 raid1
│   ├─vg0-root 252:0    0   9.3G  0 lvm   /
│   ├─vg0-var  252:1    0   3.7G  0 lvm   /var
│   └─vg0-swap 252:2    0   7.5G  0 lvm   [SWAP]
└─sda3           8:3    0   419G  0 part
sdb              8:16   0 447.1G  0 disk
├─sdb1           8:17   0   243M  0 part
│ └─md0          9:0    0 242.8M  0 raid1 /boot
├─sdb2           8:18   0    28G  0 part
│ └─md1          9:1    0  27.9G  0 raid1
│   ├─vg0-root 252:0    0   9.3G  0 lvm   /
│   ├─vg0-var  252:1    0   3.7G  0 lvm   /var
│   └─vg0-swap 252:2    0   7.5G  0 lvm   [SWAP]
└─sdb3           8:19   0   419G  0 part
What I do not understand is how this (disk io/rw limits) would work at all considering zfs can be mirror, raindz, raidz2 etc consisting of 2+ hdd (block devs)
If CT's root would sit at zvol then there would be MAJ:DEV device but when CT is only partition located on zpool then for all disks used in this zpool there would have to be blkio.throttle.write_bps_device set?
ZFS spreads I/O in "unpredictable ways" so if one would like to set 100iops limit for CT located at zpool consisting of 4 disks raidz2 how would u set this value for each of disk?

So the way blkio limits work on Linux suck quite a bit and LXD tries to do the best it can, the current logic is:

Figure out all blocks that support limits
Guess what block or blocks the container path is using
Apply the limit to all the blocks

There are some obvious problems with that:

It requires the filesystem to go through the normal kernel block interface. That's unfortunately not the case for all the ZFS code paths which bypass the normal blkio pipeline and also the kernel page cache in favor of the Solaris equivalents through spl.
As partitions cannot have limits themselves, limits are applied on the parent device, this is potentially odd because of the next point.
As limits are block based and not path based, if the same block is used by multiple paths with different limits, then there's no way for LXD to enforce the limits as specified, instead it will average them and apply the result to the block device.

It's really a case of trying to do the best we can with the interface provided to us by the kernel. If you want things to work perfectly, you'd need all mounts that have limits associated to be coming from separate block devices which aren't partition and aren't using zfs, but that's pretty difficult :)

Thank you very much for such a fast answer.
I asume setting limits.disk.priority (is it mapped to cgroup blkio.weight?) would work as expected even for zfs?
Just out of curiosity I'll try seting CT root on a zvol @monday and check if blkio.throttle.* will work this way (first I must RTFM how to do it ;)).

I would expect disk.priority to work yeah as that sits a bit further down the pipe and I'd expect zfs to go through that particular pipe too.


Add ERC20Votes

Work in progress.
Fixes #631.

[x] Tests
[ ] Tried the feature on a public network
[ ] Documentation

I think the PR has enough tests already to be ready for review. Still, there are a couple of things missing (pending):

Test ERC20 events in the ERC20Votes preset. My plan is to add this after #677 gets merged.
Test specifically ERC20 new hooks logic. My plan is to also add this after merging #677. Current tests ensure this flow is working, but tests in ERC20 should be added.
Add delegateBySig to the IVotes interface, and implement it. This shouldn't be a problem, but I wanted to ensure that the rest of the logic was working as expected first.
Answer the gas optimization open questions in comments (and in general), and optimize the code for gas efficiency.

I'd like to point out a rather big discrepancy between the Solidity version and the current version on this PR: the use of ERC5805 (FutureLookup).
In this PR, we use the current timestamp as a reference. The Solidity version uses the clock() function.
I don't know if this has already been discussed or if there's a rationale on choosing timestamp rather than block_number ?

I couldn't find documentation about block times in Starknet so I got some data from the last 12 hours of blocks and I found that it seems to vary quite a lot.

In Ethereum/Solidity the use of block numbers as a way to measure time is sort of justified because the chain has a constant block time, and even then we are moving towards timestamps because as the merge has shown block time can be changed and affect time periods defined in terms of block numbers. In Starknet this seems to be even worse, if my data above is correct, with highly variable block times under normal conditions. These are pretty strong reasons to use timestamps only in this environment in my opinion.
@pscott Let us know your perspective.

@frangio Thanks for the prompt response! :)
I agree timestamps looks more useful and should be the way to go. We thought it would be useful to point out the discrepancy though, as some users might expect the SN version to work the same way as the Solidity version :)


[FEATURE] buffered channel drain

Summary
Refactor go plugins to drain messages with buffering.
Description
This PR refactors the cshared layer so that it uses a buffered go channel. This improves the throughput tremendously.
This is part of an effort to previously improve the S3 plugin during a PoC.

I have an image on my docker hub that should work with core and has the necessary modifications: pwhelan/fluent-bit:s3-super-faster.
It's based on vanilla fluent-bit to avoid this patch that core-fluent-bit has: https://github.com/calyptia/core-fluent-bit/blob/main/patches/07-fix-for-issue-175.gitpatch since calyptia/plugin#34 supersedes it. This is necessary to avoid the write to ring buffer error.
If it fails to work on core for any reason just dump a pod log and I'll see what I can do.

With unbuffered channel + the milisec block in core-fluent-bit we are achieving the same at the fluent-bit side.

When using a single coroutine to ingest records on the golang side the throughput should be mostly at parity. This code mostly looks to workaround the lock at the C level when ingesting messages to the C side as well as allowing higher throughput when using multiple coroutines.
I have a branch of the s3 replay plugin which uses a set number of coroutines to process each file in a bucket which is helped quite a bit by this branch.

This PR is superseded by #43 .


Make consistent the criteria for daily pipeline jobs

For example the criteria for JS' PublishPackages job which publishes dev packages is:
or(eq(variables['SetDevVersion'], 'true'), and(eq(variables['SetDevVersion'], ''), eq(variables['Build.Reason'],'Schedule'), eq(variables['System.TeamProject'], 'internal')))

While the .NET criteria for the similar PublishPackages job is:
or(eq(variables['SetDevVersion'], 'true'), and(eq(variables['Build.Reason'],'Schedule'), eq(variables['System.TeamProject'], 'internal')))

It's unclear whether these criteria are different. They should be made as consistent as possible to smooth the process of editing these pipelines.

I don't believe eq(variables['SetDevVersion'], '') is interesting in the second part of this condition. It probably doesn't hurt the execution in our scenarios because we don't set that variable as a global variable for our scheduled builds, but it would be nice to remove it here as it just makes the conditions more complex then it needs to be.

Indeed it is no longer relevant -- https://github.com/Azure/azure-sdk-for-js/pull/11476#issuecomment-699395920
The expression in .NET, Java, and Python are all the same, only JS is different

Triaging this... we're pretty sure that you (@danieljurek) have already fixed the place(s) where this happens.  If there is broader tools work to do here, please reassign to @chidozieononiwu.

Oh yes, this is merged here and it only impacts JS -- https://github.com/Azure/azure-sdk-for-net/pull/24199
Closing.


Lookup no longer returns results when intermediary nodes in hierarchy are omitted

Please select the area your Bug applys to. (Multiple selections are Possible)

[ ] Onboard. Initial vault setup and import/export pods
[x] Create. Note creation, lookup, snippets and templates
[ ] Retrieve. Backlinks, references, graph view
[ ] Structure. Refactoring, multi-vault and schemas
[ ] Publish. Sharing your repo with the world
[ ] Misc (Choose this if your not sure)

Describe the bug
I have a hierarchy javascript.lang.feat.this, and as per expected logic of the Lookup tool, should be able to find that note by simply entering javascript.this. However, this is not the case.
To Reproduce
Steps to reproduce the behavior:

Create a hierarchy of 4 levels
attempt to retrieve the 4th level by entering only the first and fourth in the lookup tool
notice that the note does not appear as expected

Expected behavior
The fourth hierarchy note should appear in the Lookup results.
Desktop (please complete the following information)

OS: MacOS
Browser: Chrome
Version: v0.61.0

I'm not sure if this is related, but I'm also observing other odd behaviour. Perhaps I misidentified the actual circumstances under which this bug occurs.
I have a hierarchy with total 2 notes:

svelte
svelte.sveltekit

When I enter svelte in the Lookup tool, I see just the top-level note (svelte).
When I enter svelte.sveltekit in the lookup tool, there are no results, and hitting  overwrites my existing svelte.sveltekit note with an empty note.