Add __OW_ACTION_VERSION in action metadata

In many cases (e.g. caching), it would be useful that the action code would be able to access the action version in something like __OW_ACTION_VERSION. For example, this would allow a developer to create cache keys that would contain the action version and would change after each deployment.
@rabbah On Slack you also mentioned maybe adding some hash to make sure that undeploying and redeploying an action would not recreate similar version numbers, so something like 0.0.1-1a2b3c4d and 0.0.1-9f8e7d6c.
I can try to create the PR, never did any Scala but it doesn't look very complicated for that little change ... except I'm not sure about the hash. Any idea here?

We can start without the hash :) please holler if you need a pointer where to look.
For posterity the version is set automatically in the controller so that every update increments the semver but a delete followed by create resets the semver to 0.0.1.
A hash could help but if an action is deleted and recreated identically and the hash is based on a digest of the bits and no other metadata (timestamp?) it could be identical and defeats the versioning being always unique.
There is also the question where to compute the digest/hash as it can consume cycles on a critical path for create/update.

Closed by #4761


set allchunks: true for ExtractTextPlugin

fixes https://github.com/facebook/create-react-app/issues/3086 https://github.com/facebook/create-react-app/issues/2415
prior discussion https://github.com/facebook/create-react-app/issues/408
more details of this behavior https://github.com/webpack/webpack/issues/673

Thanks for the PR.  With the new Webpack 4 integration CRA is no longer using ExtractTextPlugin.


This is blocked on https://github.com/drud/ddev-live/issues/331
Steps to Reproduce:
Version and configuration:
Related links or issues:
Definition of Ready Checklist:

[ ] Provides steps to reproduce
[ ] Dependencies identified
[ ] Sized by team

RProduct Owner AScrum Master CEng. Lead ITeam
Definition of Done Checklist:

[ ] Deployed on test environment
[ ] Steps do not reproduce
[ ] Unit test and E2E coverage updated (if applicable)
[ ] Builds without errors
[ ] Internal documentation updated (if required)

REng. Lead, Team AScrum Master CIProduct Owner

DDEV-Live is no more, so closing.


Typo in Android Development Section

Describe the bug
There is a typo error in the Android Development section, point number 8.
To Reproduce
Steps to reproduce the behavior
Expected behavior
Instead of "8. Now thay you've learned let's build it Project 1" it should be "8. Now that you've learned let's build it Project 1"
Screenshots

Additional context
Add any other context about the problem here.

@hasnainmakada-99 can you assign me this issue ?

Here you go, @Arbtrage


Ability to push all apps in a manifest.yml in parallel

This would be useful for microservice architectures.

Saved you a click: "literally in parallel"

@dkoper: What do you think about this?

Let me confirm the issue currently - pushing multiple apps is too slow? And if we would upload the bits in parallel, it will be fast?
@tsaleh Would you happen to have a breakdown of the push process showing how much time is spent on uploading vs other steps?
Would there be any circumstances under which you'd want to push apps sequentially?

Saying "in parallel" may have been a mistake on my part.  The point of this isn't about speed, but about the ability to push all of the apps defined in a manifest easily and quickly.  Doing it in parallel would be a nice optimisation, but what I'm really looking for is cf push --all.

@tsaleh Apologies in the delay. How does cf push -f app-manifest-with-multiple-apps not already provide this?

It does.  I think it didn't when I opened the issue?
...now, how about doing it in parallel?  :D:D:D  Should that be a separate GH issue?

You'd probably submit an issue with the same title? We may as well re-use this one :)
So far we have no API calls that we make in parallel. I have listed my initial concerns with it here:
https://github.com/cloudfoundry/cli/pull/805#issuecomment-218371703
That said, with the upcoming Bits Service, uploading of artifacts will no longer put a load on the Cloud Controller, and may even allow uploading directly to a blobstore. We could experiment if significant performance improvements are made by parallelizing uploads.

This is a feature I would also like.  For us, it is not the artifact uploading serially that is slow, but that we have to wait for each app to start before the next one stops and restarts.
For instance, we are deploying 7 Spring apps in a sandbox environment that we run our smoke tests against.  Across uploading, stopping, and starting each application, our total deploy time takes 10+ minutes.  If each app were starting in parallel, then the deploy time will only be as long as the longest application deployment.
We can currently hack around this in our CI environment by having different jobs for deploying with individual manifests, but it really feels more like a workaround when we want to deploy all of the applications as a bundle (at least for smoke testing).

@butzopower @tsaleh
A UX concern with this is how to display the current output and CF logs when we're retrieving staging logs and polling multiple apps at the same time.
Also, we wouldn't want to change the current sequential behaviour as (micro-service based) applications may depend on it: defining the backend services at the top of the app manifest and the front-end app last to ensure everything's running by the time the external facing app is up.
Have you considered using --no-start in your app manifest and rely on your shell to start them simultaneously? Something like:
cf push -f app-manifest.yml --no-start && cf start one-app & && cf start another-app & && cf start yet-another-app & && cf start the-final-app && wait?
with an additional check to only start your smoke tests if all apps started successfully
This has the advantage that you could send the trace for each app start to a different file by just prepending CF_TRACE=one-app etc. before the start commands.

Any progress on this? Would be nice to push 10 of our apps in parallel.

@DarrylD I see many complexities (mentioned in my previous comment) that need to be resolved and I wonder how these could be resolved in a way that keep this feature as useful and usable as people expect.
I'd rather see someone in the community develop a CLI plugin for this feature, and make it useful for their use case. If it turns out widely-adopted and well-liked, we can use that as a model to consider providing it in the core CLI.

Is there any of this new how to build this ? I think this is a useful feature


Failed to compile substrate node wasm-test when using zld as a linker on macOS

Hello, I'm facing an issue when trying to build our substrate node on macOS and using zld as a default linker to speed the build process.
Here is my .cargo/config.toml looks like:
[target.x86_64-apple-darwin]
rustflags = ["-C", "link-arg=-fuse-ld=/usr/local/bin/zld", "-Zshare-generics=y"]

Here is the error I get when I try to run cargo build --release
error: failed to run custom build command for `darkwebb-standalone-runtime v0.1.0 (/Users/shady/github/webb-tools/protocol-substrate/standalone/runtime)`

Caused by:
  process didn't exit successfully: `/Users/shady/github/webb-tools/protocol-substrate/target/release/build/darkwebb-standalone-runtime-a6bc96a030e9dc71/build-script-build` (exit status: 1)
  --- stderr
  Rust WASM toolchain not installed, please install it!

  Further error information:
  ------------------------------------------------------------
     Compiling wasm-test v1.0.0 (/var/folders/1q/rvg2xqc1049dtn0vkt3b7m8w0000gn/T/.tmpdw0RUP)
  error: linking with `rust-lld` failed: exit status: 1
    |
    = note: "rust-lld" "-flavor" "wasm" "--rsp-quoting=posix" "--export=__heap_base" "--export=__data_end" "-z" "stack-size=1048576" "--stack-first" "--allow-undefined" "--fatal-warnings" "--no-demangle" "--no-entry" "--export-dynamic" "/var/folders/1q/rvg2xqc1049dtn0vkt3b7m8w0000gn/T/.tmpdw0RUP/target/wasm32-unknown-unknown/debug/deps/wasm_test.3s3w9cfol5vlw2gb.rcgu.o" "/var/folders/1q/rvg2xqc1049dtn0vkt3b7m8w0000gn/T/.tmpdw0RUP/target/wasm32-unknown-unknown/debug/deps/wasm_test.1eqca4a22iuwkgax.rcgu.o" "-L" "/var/folders/1q/rvg2xqc1049dtn0vkt3b7m8w0000gn/T/.tmpdw0RUP/target/wasm32-unknown-unknown/debug/deps" "-L" "/var/folders/1q/rvg2xqc1049dtn0vkt3b7m8w0000gn/T/.tmpdw0RUP/target/debug/deps" "-L" "/Users/shady/.rustup/toolchains/nightly-2021-11-10-x86_64-apple-darwin/lib/rustlib/wasm32-unknown-unknown/lib" "/Users/shady/.rustup/toolchains/nightly-2021-11-10-x86_64-apple-darwin/lib/rustlib/wasm32-unknown-unknown/lib/libstd-34bc94a57ca06760.rlib" "/Users/shady/.rustup/toolchains/nightly-2021-11-10-x86_64-apple-darwin/lib/rustlib/wasm32-unknown-unknown/lib/libpanic_abort-6f9161e746ec4a5c.rlib" "/Users/shady/.rustup/toolchains/nightly-2021-11-10-x86_64-apple-darwin/lib/rustlib/wasm32-unknown-unknown/lib/libdlmalloc-bcaeb89600b2d568.rlib" "/Users/shady/.rustup/toolchains/nightly-2021-11-10-x86_64-apple-darwin/lib/rustlib/wasm32-unknown-unknown/lib/libstd_detect-8eb480a31e133ca8.rlib" "/Users/shady/.rustup/toolchains/nightly-2021-11-10-x86_64-apple-darwin/lib/rustlib/wasm32-unknown-unknown/lib/librustc_demangle-ed5d049f80c21cf0.rlib" "/Users/shady/.rustup/toolchains/nightly-2021-11-10-x86_64-apple-darwin/lib/rustlib/wasm32-unknown-unknown/lib/libhashbrown-29401705131a5d1e.rlib" "/Users/shady/.rustup/toolchains/nightly-2021-11-10-x86_64-apple-darwin/lib/rustlib/wasm32-unknown-unknown/lib/librustc_std_workspace_alloc-2449ff2aab411d5b.rlib" "/Users/shady/.rustup/toolchains/nightly-2021-11-10-x86_64-apple-darwin/lib/rustlib/wasm32-unknown-unknown/lib/libunwind-268bb889ff3f7e62.rlib" "/Users/shady/.rustup/toolchains/nightly-2021-11-10-x86_64-apple-darwin/lib/rustlib/wasm32-unknown-unknown/lib/libcfg_if-8a6fc3c84b246983.rlib" "/Users/shady/.rustup/toolchains/nightly-2021-11-10-x86_64-apple-darwin/lib/rustlib/wasm32-unknown-unknown/lib/liblibc-f59cfb9291c841eb.rlib" "/Users/shady/.rustup/toolchains/nightly-2021-11-10-x86_64-apple-darwin/lib/rustlib/wasm32-unknown-unknown/lib/liballoc-6bbf5d485df4d727.rlib" "/Users/shady/.rustup/toolchains/nightly-2021-11-10-x86_64-apple-darwin/lib/rustlib/wasm32-unknown-unknown/lib/librustc_std_workspace_core-10bf4b0039d4de0f.rlib" "/Users/shady/.rustup/toolchains/nightly-2021-11-10-x86_64-apple-darwin/lib/rustlib/wasm32-unknown-unknown/lib/libcore-3365b6c50e94718e.rlib" "/Users/shady/.rustup/toolchains/nightly-2021-11-10-x86_64-apple-darwin/lib/rustlib/wasm32-unknown-unknown/lib/libcompiler_builtins-4c6e1466f9f1beb8.rlib" "-L" "/Users/shady/.rustup/toolchains/nightly-2021-11-10-x86_64-apple-darwin/lib/rustlib/wasm32-unknown-unknown/lib" "-L" "/Users/shady/.rustup/toolchains/nightly-2021-11-10-x86_64-apple-darwin/lib/rustlib/wasm32-unknown-unknown/lib/self-contained" "-o" "/var/folders/1q/rvg2xqc1049dtn0vkt3b7m8w0000gn/T/.tmpdw0RUP/target/wasm32-unknown-unknown/debug/deps/wasm_test.wasm" "--gc-sections" "--no-entry" "-O0" "-fuse-ld=/usr/local/bin/zld"
    = note: rust-lld: error: unknown argument: -fuse-ld=/usr/local/bin/zld

  error: could not compile `wasm-test` due to previous error
  ------------------------------------------------------------

warning: build failed, waiting for other jobs to finish...

Any idea on how to configure the substrate_wasm_builder to skip that and not use that linker? as it try to use it for wasm, which I guess is not supposed to be used there!
I've also opened an issue at zld here: https://github.com/michaeleisel/zld/issues/95 but was asking for any help or hint I could do.
Our code that I'm trying to compile: https://github.com/webb-tools/protocol-substrate

Please try latest master. It should be fixed there.
This pr: https://github.com/paritytech/substrate/commit/0214f26b5fb6afb89b5322aa59e18b1d19e88a54

Thank you, trying that now.

Thanks that worked for me!


chore: appease linters!

This appeases the various linters

@ManasviGoyal could you merge this? :)

@ManasviGoyal could you merge this? :)

Yes, Sure!


Eager navigation and load handling of cancel

Describe the bug
When you navigate back before the loading has finished, the behavior of the app gets broken.
To Reproduce

In 03-Navigation-Lists-NavigateAndLoad.swift on line 46 set the delay a bit longer (e.g. 3 seconds)
Run the demo
Select "Load optional counter that starts from 1"
Navigate back from the screen before the counter appears
Now try to open the same counter again or any of the others

Observed behavior
Tapping same counter is unresponsive. Tapping other counter immediately navigates back.
Screen Recording 2020-05-24 at 11.36.09.zip
(Unfortunately GitHub won't let me upload screen recording unzipped.)
Expected behavior
Being able to use the demo as if you had waited until the counter had appeared.
Environment

Xcode 11.5
iOS 13.5
Simulator for iPhone SE (2nd generation)

@johankool I just happen to be playing in that code today and found that if you just move one line out of the if let block, it works fine, the reason is that since the counter isn't loaded yet, it fails the second let case but the selection still needs to get nil'd out:
At around line 50, I think it should look like this, note the state.selection = nil is moved out of the if block:
    case .setNavigation(selection: .none):
      if let selection = state.selection, let count = selection.value?.count {
        state.rows[id: selection.id]?.count = count
      }
      state.selection = nil
      return .cancel(id: CancelId())

@pcolton That indeed fixes it. Thanks!
I noticed btw that also 03-Navigation-Lists-LoadThenNavigate has similar issues.

For 03-Navigation-Lists-LoadThenNavigate an easy fix eludes me, so I'll leave it up to the big guns to fix that. ;-)

It was a trickier fix, but in #130 we did a workaround to force the root view to recreate fresh case studies each time it appears. In a real application you'd have to propagate that cancellation or niling out of state to when parent navigation is handled. Hopefully navigation becomes a lil less thorny in the next version of SwiftUI!


Rare bug for stall on demand

Currently I'm facing an issue when stall_on_demand=true (if false it disappears). It is very rare and hard to reproduce in a unit test.
The reason is likely in DijkstraBidirectionCH.entryIsStallable:
adjNode.weight + weighting.calcWeight(iter, !reverse, getIncomingEdge(entry)) < entry.weight

It returns true although it should return false. In my case it is the 4th decimal place: 35.643+50.2975 < 50.297522
So, when I round to the precision we currently use in CHGraphImpl:
Math.round(entry.weight / 1000f) * 1000f
the problem disappears. But maybe it is related to virtual nodes because the special case is a QueryGraph with 3 locations where the fastest route B->C crosses point A.

Thanks a lot for debugging, I am sure this took a lot of time to figure out. Quite suprisingly I think I ran into the same issue recently and could narrow it down to this:
map: core/files/andorra.osm.pbf
query: http://localhost:8989/maps/?point=42.486984%2C1.493152&point=42.479172%2C1.492451&point=42.577133%2C1.458908&locale=en-US&vehicle=car&weighting=fastest&elevation=false&stall_on_demand=true&use_miles=false&layer=Omniscale
It is also related to the via point (removing it or even changing the order of the points) makes the problem dissapear, just as well as setting stall_on_demand to false.
Interestingly this problem does not happen on more recent versions of the same map (the oldest I found was still from 2018), so might be an option to diff the maps to see what has changed.
If it turns out that the problem is due to the floating point number comparison I think we could simply use some epsilon in the above condition.

So, when I round to the precision we currently use in CHGraphImpl:

What did you round exactly ?

Interesting, indeed :) !

Exactly which numbers did you round ?

I meant that I used
adjNode.weight + weighting.calcWeight(iter, !reverse, getIncomingEdge(entry)) < Math.round(entry.weight / 1000f) * 1000f
// (We could also use `entry.weight - 1/1000f`)

instead of
adjNode.weight + weighting.calcWeight(iter, !reverse, getIncomingEdge(entry)) < entry.weight

The reason for the 1000f is the precision we use for the shortcut weight in CHGraphImpl. I also think that we could reduce the change that this happens via increasing the precision of the shortcut weight #1544.
Another wild guess for the reason: the shortcut weight precision is limited to the 1000f compared to the very precise weight calculated from two VirtualEdgeIteratorState's?

Another wild guess for the reason: the shortcut weight precision is limited to the 1000f compared to the very precise weight calculated from two VirtualEdgeIteratorState's?

I also remember recently having problems with virtual edges that did not seem to have the right distance (I'm on it :))

I have a failing integration test here: https://github.com/graphhopper/graphhopper/tree/issue_1574
There are many ways to make it pass:

as @karussell suggested fixing the stall on demand condition (rounding)
do not add geometries during parsing the map
do not set roundabout bits during parsing
increasing the min subnetwork size

I have tried to reproduce the problem by building the graph manually using graph.edge... using the output of GHUtility.printGraphForUnitTest, but unfortunately to no avail so far :(

Math.round(entry.weight / 1000f) * 1000f

It should be Math.round(entry.weight*1000f)/1000f, probably what you meant. The other formula returns zero for all weights < 1000, so basically always (-> nothing gets stalled).
Anyway I am now 99.9% sure think I finally understood the problem and it is related to CH/stall-on-demand and virtual via nodes. Removing the geometries, not using the roundabout bit or using another subnetwork size only fixes the problem because another hierarchy is created I guess.

probably what you meant.

Ups! Sure!

I have a failing integration test here: https://github.com/graphhopper/graphhopper/tree/issue_1574

Great. Will also have a look and guess about it

https://github.com/graphhopper/graphhopper/blob/f63b30ccbf37d9558c830b61a7608d3bc19b4a2c/core/src/test/java/com/graphhopper/routing/ch/PrepareContractionHierarchiesTest.java#L425-L434

I am wondering if an option would be to set the CH level of virtual nodes to the minimum CH level of their neighbornodes (can be virtual nodes as well). Right now we do this (imagine the vertical position to represent the CH level) and x to be virtual nodes (could be multiple).
           b
  a

    x x x

which allows going 'down' from a to b because of the virtual node(s). so instead do this:
            b
  a  x x x

This way the virtual nodes should not change the behavior of CH ? Another way would be to ignore via virtual nodes completely: first find the closest 'real node' from virtual start/target nodes on the query graph, ther run CH on the plain CH graph (without virtual edges). Finally we could of course try to fix the rounding in certain places...

I could reproduce the bug in a unit test with only 8 nodes, it is quite involved

Really great you got something recreated :+1:

I am wondering if an option would be to set the CH level of virtual nodes to the minimum CH level of their neighbornodes

Sounds reasonable but why would this fix the problem? Isn't this even more restrictive?

first find the closest 'real node' from virtual start/target nodes on the query graph, then run CH on the plain CH graph (without virtual edges)

This is cumbersome. I tried this for non-CH (i.e. without the QueryGraph logic) but the search got too complex. Best thing would be of course we could hide the virtual node complexity for the algorithms (but this is also not fully possible for landmarks)


Translation extension, what's the priority?

Trying to translate field from base app -> Sales Invoice list name
The problem is that other extension which is added to dependency in our extension also translate this field name, but we want to change it to other translation. Even if we tried add caption to this field the higher priority translation is comming from the dependent extension.
How to do it and what's the priority in xlf. file means?
Does it have any influence ?
<trans-unit id="PageExtension<PHONE_NUMBER> - Property<PHONE_NUMBER>" size-unit="char" translate="yes" xml:space="preserve" al-object-target="Page<PHONE_NUMBER>">           <source>Sales Invoice</source>           <target>Faktura sprzedaży</target>           <note from="Developer" annotates="general" priority="3"></note>           <note from="Xliff Generator" annotates="general" priority="3">PageExtension LST_SalesInnvoicePageExt - Property Caption</note>         </trans-unit>

Hi @devzom,
If they have taken a dependency on your app then it means they are resolved after yours and if you want the application translated a certain way I would suggest that you make a new app that depend on their app which supplies the wanted captions. Note that you don't need a page extension to change the caption of a page, see the docs Translating other extensions.
The main mechanism for controlling the resolution order is by dependencies.

Hello, regarding the priority setting in the .xlf file, this is an .xlf syntax support only and not used in connection with Business Central. Hope this and the reply above answers your question, so closing this issue. Thanks.


[Android] Implement XWalkView.setUserAgentString

Implement API XWalkView.setUserAgentString for client to set it's own user agent.
BUG=XWALK-3306

@lincsoon @halton @wang16

Does it need a @since?

@rakuco @kenchris @wang16

A test case is preferred.

@wang16 Add test case

LGTM, thanks.


Ability to modify flow lines while being drawn/determine points along flow lines

Not sure if you're taking any sort of feature requests (and recognizing that this project is open source I should really just be taking it upon myself to work on solving this problem), but it would be amazing to be able to either modify flow lines as they are being drawn (perhaps a callback with the ability to intercept each segment of the line), and/or deterministically get coordinates along a flow line easily.
Apologies if the ability to do either of this things is already present in the library, or if there is math Im unaware of afford the latter idea.
Absolutely loving the library so far, excited for it's future and hopefully contributing at some point!

Hey @jcquinlan
I don't know if I'm understanding your message correctly, but I think you might be able to do just what you need with the Position class: https://github.com/acamposuribe/p5.brush?tab=readme-ov-file#exposed-classes
The Position class lets you create a new coordinates object with new brush.Position(x,y), which you can then move through the flowfield, whatever distance you want. This is equivalent to how flowlines are drawn. The only thing is that if you want to move exactly following a flowline, you need to know the step_length for that specific brush type.
You can use the brush.Position class like this:
`
// Let's set the HB
brush.set("HB", "black", 1)
// Let's draw a "horizontal" 0 degrees flowline starting at (10,30), of 100px length
brush.flowLine(10, 30, 100, 0)
// Let's say we want to find the coordinates in these path, every 10px
let coordinates = []
// We create a Position object in the starting coordinates
let pos = new brush.Position(10,30)
// We move 10px through the 0 degrees path
// It's important to notice that this movement is cumulative, that is,
// once the position has been moved, its coordinates are updated
for (let i = 0; i < 10; i++) {
pos.moveTo(10, 0)
coordinates.push([pos.x, pos.y])
}
// This are the 10 points through the flow path
console.log(coordinates)
`
I hope this helps!
(I'm pushing a small change to the code in order to make this work better, since I just found a small problem)

In any case, if what you want to do is draw a series of segments with different sizes and different directions, it's probably much easier to use the Plot class, that lets you create just that!
To be honest, the documentation for the three exposed classes is very minimal, but these are basically the core of the whole library. If you learn to use them, you can do almost everything

Circling back on this to say A.) thanks for pointing me in the right direction, as the Position class indeed allowed me to do what I was thinking originally, and B.) apologize for not having more thoroughly explored the docs before creating an issue!
I'll close the issue now, thanks for all your hard work!


Font settings not saved

Hello, thanks for the tool.
I want to increase the font size, but after restart the program, the font size was reset to default.
I also tried "Save Configuration..." but I didn't see the font settings in the DebugView++.dbconf file.

Hm thanks for reporting :)
On Tue, Aug 14, 2018, 20:28 tmplinshi<EMAIL_ADDRESS>wrote:

Hello, thanks for the tool.
I want to increase the font size, but after restart the program, the font
size was reset to default.
I also tried "Save Configuration..." but I didn't see the font settings in
the DebugView++.dbconf file.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/CobaltFusion/DebugViewPP/issues/330, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AFqJhOAwGmj7X6Jq6C3ffH16M_rkwsskks5uQxbHgaJpZM4V88ml
.

Ok, I found the reason. It's when no font name were selected, then the font settings won't saved.

I cant seem to get into a scenario when no font is selected? I tried removing everything from the registry, but even then still a default font is always selected. What windows version are you on? maybe its a version specific thing?

I'm using Windows 10 x64 (Chinese language), the default font name "宋体"  is
in Chinese characters, maybe it's because of the font name?
Jan Wilmans<EMAIL_ADDRESS>于 2018年8月17日周五 下午4:01写道：

I cant seem to get into a scenario when no font is selected? I tried
removing everything from the registry, but even then still a default font
is always selected. What windows version are you on? maybe its a version
specific thing?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/CobaltFusion/DebugViewPP/issues/330#issuecomment-413789596,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEPpxIJN_ss2W4aOednd0PcdZdeaOOGeks5uRnh1gaJpZM4V88ml
.

Ah, maybe its a character conversion problem, I will look into that.
So you do you get into the issue, you just start debugview++, open the font
selector and the default selection is then empty?
Greetings,
Jan
On Fri, 17 Aug 2018 at 10:15, tmplinshi<EMAIL_ADDRESS>wrote:

I'm using Windows 10 x64 (Chinese language), the default font name "宋体" is
in Chinese characters, maybe it's because of the font name?
Jan Wilmans<EMAIL_ADDRESS>于 2018年8月17日周五 下午4:01写道：

I cant seem to get into a scenario when no font is selected? I tried
removing everything from the registry, but even then still a default font
is always selected. What windows version are you on? maybe its a version
specific thing?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/CobaltFusion/DebugViewPP/issues/330#issuecomment-413789596
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AEPpxIJN_ss2W4aOednd0PcdZdeaOOGeks5uRnh1gaJpZM4V88ml
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/CobaltFusion/DebugViewPP/issues/330#issuecomment-413792667,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFqJhFyewtQ3318ctaCvZlmLrIzzQqnRks5uRnukgaJpZM4V88ml
.

--
Jan

That's correct :)

I have checked the registry, the value of FontName is empty.

could you try again on v<IP_ADDRESS> ? I fixed some conversion functions for #328 and I wonder if they also solve this problem?

Thanks, just tried it, but the issue remains. For now I can select a font to solve the issue.

I can't reproduce it, but I think this happens because then 'system default' font is read/converted into an empty string. Since it is very easy to work around (just select a font), I'm going to close this issue


New suggestions are not pushed in production environment

New titles were not being pushed to the client in the production environment -- title view.
Needs reproduction.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/32278123-new-suggestions-are-not-pushed-in-production-environment?utm_campaign=plugin&utm_content=tracker%2F345420&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F345420&utm_medium=issues&utm_source=github).

Was able to reproduce this on my new workstation. The host config was not setup correctly, resulting in new title triggers getting sent to nonexistent hosts. Relevant:
config: https://github.com/rikai/Showbot/blob/devel/cinchize.yml.example#L8
trigger: https://github.com/rikai/Showbot/blob/devel/lib/cinch/plugins/suggestions.rb#L42

Should check for trailing slash to prevent double slash at beginning of request path:
https://github.com/eriknelson/Showbot/blob/devel/lib/cinch/plugins/suggestions.rb#L42
Confirmed it's actually hitting the trigger, endpint is returning a 500 on an unhandled exception. Traceback:
https://gist.github.com/rikai/3efcae933023b8643c8bf25af4851d9c


before_hook fails on run-all apply but not on standard apply

We have a fairly large set of layered directories for our terragrunt configurations, and often run cross-cloud terraform, while maintaining all state in AWS S3.
One issue we need to code against is making sure that the terragrunt being run is in the right environment/account for where it's applying resources.  If it's not, but connected to AWS S3 and the correct backend, terraform will run and assume the resources don't exist, say they are deleted, and clear the TF State file.  While we can preserve the older state file with bucket versioning, we'd also like to just have a before_hook check that we're in the right environment.
We have created a before hook, like so:
before_hook "validate_azure_env" {
    commands    = ["apply", "destroy", "plan"]
    execute     = ["./validate-acct.sh", "azure", "${local.azure_account_alias}"]
    working_dir = "${path_relative_from_include()}/tools"
  }

Per the above, the script resides in the top/root directory inside the 'tools' folder.  Every terragrunt.hcl that we're applying has the following include:
include {
  path = find_in_parent_folders("root.hcl")
}

When I run terragrunt apply in a module directory, everything works as expected.
However, when I run terragrunt run-all apply from a parent folder to run multiple modules, all calls to the script fail:
Error running hook validate_azure_env with message: chdir ../../../../../tools: no such file or directory  prefix=[/Users/awiesner/git-v2/ego-infra/azure/staging/eastus2/aws/route53]

This shows up for each module (with the pathing adjusted, as appropriate for it's location in the folder hierarchy) and the paths are actually correct based on the location of the module.
My assumption here is that the underlying module is correctly triangulating where the validate-acct.sh file is in relation to the terragrunt config, but the chdir command being run is not happening from that module directory, but from where terragrunt run-all apply is being run.

Are you trying to get to the directory where the root.hcl is defined? If so, get_parent_terragrunt_dir is the right function for this, not path_relative_from_include, as that returns an absolute path.

Thank you, @yorinasub17.  My misunderstanding in reading the docs.


[stable/grafana] Unable to set Grafana Env Var

Attempting to create an entry fro a Grafana environment variable causes an error:
    grafana:
      enabled: true
      env:
        - name: GF_FOO
          value: bar

Results in:
ts=2020-06-22T17:28:02.984996473Z caller=release.go:292 component=release release=prometheus-operator targetNamespace=monitoring resource=monitoring:helmrelease/prometheus-operator helmVersion=v3 error="upgrade failed: template: prometheus-operator/charts/grafana/templates/secret.yaml:1:58: executing \"prometheus-operator/charts/grafana/templates/secret.yaml\" at <.Values.env.GF_SECURITY_ADMIN_PASSWORD__FILE>: can't evaluate field GF_SECURITY_ADMIN_PASSWORD__FILE in type interface {}" action=upgrade
The same is true fro setting by SecretKeyRef, including setting the GF_SECURITY_ADMIN_PASSWORD__FILE  variable itself.

i'm also facing the same issue

+1

i found the solution, actually env expects an object, not an array, so you need to do --set grafana.env.key1=value1 --set grafana.env.key2=value2 or,
grafana:
  enabled: true
  env:
    key1: value1
    key2: value2

FWIW this also happens in the stable/grafana chart. Here's my values:
grafana.ini:
  database:
    type: mysql
    name: grafana
    ssl_mode: skip-verify
    host: mysql-host-goes-here
    user: mysql-user-goes-here
    password: ${GF_DATABASE_PASSWORD} # This *shouldn't* be required, but adding it doesn't help either
    # password: the-secret-password   # This works, but we don't want to hard code secrets!
    ca_cert_path: "/etc/ssl/certs/ca-certificates.crt"
env:
  - name: GF_DATABASE_PASSWORD
    valueFrom:
      secretKeyRef:
        name: grafana-db
        key: secret

Grafana should ideally read the GF_DATABASE_PASSWORD environment variable if it exists. The OP is trying to do the same by setting GF_FOO. In my case, we have a setup that automatically pulls secret-env variables from a vault and that setup doesn't work with grafana since the chart expects me to hardcode the secret.

Hey @andrew-pickin-epi could you add [stable/grafana] to the title?

Experiencing the same issue

experiencing the same issue

https://github.com/helm/charts/issues/22903#issuecomment-656499158 is correct. env is expected to be a map: https://github.com/helm/charts/blob/8736171868dd9ba8e73584f3fc486ee7e341718b/stable/grafana/templates/_pod.tpl#L53-L57 The pod template creates the array from the values map. IMO this is actually a good pattern for charts, because it allows an environment variable to be deleted or overwritten by key as opposed to array index which is more error prone.
Can someone experiencing this issue please verify that this works?

This is correct. 30 second test steps:
$ kind create cluster
Creating cluster "kind" ...
$ helm install issue-22903 stable/grafana --set env.FOO=bar,env.BAZ=qux
$ kubectl describe deployments.apps issue-22903-grafana

Relevant output:
Pod Template:
  Containers:
   grafana:
    Environment:
      BAZ:                         qux
      FOO:                         bar

@scottrigby I can confirm that setting env this way works. Thank you.
Was also able to read GF_DATABASE_PASSWORD from a kubernetes secret by setting:
envFromSecret: "secretName"

This chart is deprecated: https://github.com/helm/charts/pull/23662
If still applicable, please re-open issues at: https://github.com/grafana/helm-charts
Though I think this one has been answered 😄


#3832-Hotfix: Change file naming convention of the SIN validation request file

*AC
The expected file name is just BC####.OS in all environments.

[x] Do not use value from environment variable ESDC_ENVIRONMENT_CODE.
[x] No changes needed to response file handling.

I'd also add the additional AC on this one for batch number @bidyashish

The batch number update is missing in the PR. Please take care.


Add saving of group data as json file and relevant testcases

Closes #61

Codecov Report

Merging #63 (d3d4873) into dev (7b70454) will increase coverage by 0.44%.
The diff coverage is 58.13%.

@@             Coverage Diff              @@
##                dev      #63      +/-   ##
============================================
+ Coverage     57.87%   58.32%   +0.44%
- Complexity      342      352      +10
============================================
  Files            74       75       +1
  Lines          1282     1322      +40
  Branches        130      137       +7
============================================
+ Hits            742      771      +29
- Misses          487      491       +4
- Partials         53       60       +7

Impacted Files
Coverage Δ

...n/java/seedu/address/storage/JsonAdaptedGroup.java
33.33% <33.33%> (ø)

...java/seedu/address/storage/JsonAdaptedStudent.java
80.95% <80.00%> (+8.22%)
:arrow_up:

...u/address/storage/JsonSerializableAddressBook.java
84.00% <83.33%> (-2.67%)
:arrow_down:

...main/java/seedu/address/model/group/GroupName.java
70.00% <0.00%> (ø)

src/main/java/seedu/address/model/group/Group.java
29.03% <0.00%> (+3.22%)
:arrow_up:

src/main/java/seedu/address/model/AddressBook.java
72.22% <0.00%> (+5.55%)
:arrow_up:

...in/java/seedu/address/model/group/Description.java
70.00% <0.00%> (+10.00%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7b70454...d3d4873. Read the comment docs.


tests: arch: arm: Use a more common SHA algorithm

The profile type "not set" uses the "default crypto config" header. However platform may set their own crypto configuration headers. SHA-512 algorithm is not the most common algorithm to support and are for example disabled in profile types medium and small.
Change to SHA-256 which is much more common and is even needed internally by TF-M for protected storage and sub-key derivation.

@joerchan I agree SHA-256 is far more common, but looks like this broke CI as-is?

@microbuilder Works on my DK™.
It appears to be an issue that exists in the main branch also.
Looking into it.

Musca B1 board is broken, will rebase this PR once https://github.com/zephyrproject-rtos/zephyr/pull/60219 is merged.

@joerchan Want to rebase this now that the musca fixes have been merged, and I'll review? Thanks!

Rebased with Musca fix.

There are test failures for the ARM boards on this test-case.

I had to add a loop for the SHA-256 call because the interrupt work did not run after the first attempt.
I could not get other timing tweaking to work.
I don't think this is a very stable test-case. And probably a more stable test would be a custom secure service that triggered the non-secure interrupt during its execution.

I had to add a loop for the SHA-256 call because the interrupt work did not run after the first attempt.
I could not get other timing tweaking to work.
I don't think this is a very stable test-case. And probably a more stable test would be a custom secure service that triggered the non-secure interrupt during its execution.

As discussed offline, adding CONFIG_QEMU_ICOUNT_SHIFT=8 will give QEMU more time between executing instructions on a fast machine so that the interrupt isn't lost. Just as a FYI for anyone bumping in this in the future, since it's a common issue.


A block in launchDataLoad function should not have CoroutineScope receiver

It is easier when a function is either a suspend fun or an extension on CorouitineScope, so in this line of code that defines launchDataLoad function :
https://github.com/googlecodelabs/kotlin-coroutines/blob/d61b574f39bbc25af1c39686839dfaa9874a2e51/kotlin-coroutines-end/app/src/main/java/com/example/android/kotlincoroutines/main/MainViewModel.kt#L123
It would be better to define a block simply as suspending one:
private fun launchDataLoad(block: suspend () -> Unit): Job {

It should be enough for all the indended use-cases of this launchDataLoad higher order function as its block is supposed to perform some long-operation (hence suspend) and is not supposed to launch any new coroutines by itself, since the coroutine is already started by the launchDataLoad implementation (hence, we don't include CoroutineScope).
However, if the code inside the block needs to do multiple operations in parallel (that is, perform a parallel decomposition of its logic) and would need to launch additional coroutines, then it can always use coroutineScope { ... } builder that effectively converts suspend fun into CoroutineScope extension and additionally ensures that any parallel coroutines either all complete or all fail.

Thanks!
Updating codelab.


Problem with creating new Types.ObjectId  from String _id

Getting Error while Starting the application
src/logger/logger.service.ts:39:38 - error TS2554: Expected 0 arguments, but got 1.

39             user: new Types.ObjectId(user),

not sure but seems like new Types.ObjectId() doesn't expect any argument . and I am wondering if there is any way around of creating ObjectId from String

Hi @salviosage, Types.ObjectId() is a class from mongoose that use for create random object id or object id from ObjectIdString.
E.g
Let assume ObjectIdClass will return 4eb6e7e7e9b7f4194e000001 as ObjectIdString
const ObjectIdClass: Types.ObjectId = new Types.ObjectId(); // will return object id class
const ObjectIdString: string = `${_id}`; // will return 4eb6e7e7e9b7f4194e000001

In LoggerService, you must pass ObjectIdString to fill user param not the random string.
E.g
this.loggerService.info(
  ENUM_LOGGER_ACTION.LOGIN,
  'Description about the logger',
  '4eb6e7e7e9b7f4194e000001',
  [
      'login',
      'fromMobile',
      'withEmail'
  ]
);

But if my answer doesn't help you, you can give me more information about how you used LoggerService.


Optimize Vs Integration

Eliminate the hardcoded askui-shell.cmd file path.
Retain the option for other terminals to remain enabled, as it should be the user's decision.
Enable "overrideName" to ensure the terminal title consistently displays as askui-shell.
Update the icon to a robot and apply a magenta color to match the askui theme.

I think @programminx-askui can review this better than me.
Just wanted to say I love cute little stuff like the AskUI-themed Android ❤ !
Can we also get some ASCII-Art in the shell? 🥳

ASCII-Art in the shell?


Fix #28. Missing default configuration for genome in standard profile

This will fix issue #28. But -profile standard,docker still required

Thanks @tiagochst! We need to be a little careful that this doesn't break the other config profiles below, as the order of config file import is important for igenomes.config. I realise now that I hit a similar problem on the RNA pipeline recently (see |this PR](https://github.com/nf-core/rnaseq/compare/master...ewels:config_refactor#diff-c79fe4336e72c04860afccd21f4ae1c5)). I haven't tested that enough yet, but a similar refactoring could work here too.
Phil


how to create restfull api in ojs

i created a controller in Apibundle\Controller directory
then i added to Apibundle\Resources\Config\routing_rest.yml
still when i send a request i got 404; so can you explain me how can i create and develop a rest api in ojs

Related issue: https://github.com/okulbilisim/ojs/issues/844


protect real git binary by renaming examples

Some example source files such as git.go share names with common command line utilities, such as the real git. This has the unfortunate consequence that users attempting to make use of docopt.go receive a fake git binary in $GOPATH/bin that can accidentally override the real git. Especially if the position of $GOPATH/bin in $PATH occurs before the directory of the real git binary appears in $PATH. This happens because the source files in the examples/ directory are automatically built and installed by the standard go tool, such as with go get github.com/docopt/docopt.go.
Go users may wish to reposition $GOPATH/bin in their $PATH configuration, to ensure that non-Go binaries take precedence. This allows docopt.go to be used without conflicting with the regular git binary.
However, for some users a configuration with $GOPATH/bin earlier in $PATH may actually be desirable, such as when overriding system binaries with custom binaries. That's okay, we can resolve this situation as well, by renaming the git.go source file to fakegit.go. This rename allows the real git binary to continue functioning with docopt.go installed, regardless of the user's choice of ordering in their $PATH.
Some later commit could even exclude the example/ binaries from being installed to $GOPATH/bin, by refactoring the examples in terms of ..._test.go files, a common Go unit testing convention.

Yes please, the git issue specifically tends to cause issues for my new Go installs 'til I remember to delete the right binary in the gopath.

Interesting, the CI build appears to have trouble downloading the vet tool. Looks like the old vet tool has been deprecated in favor of the go vet tool now built into Go.
Vet update:
https://github.com/hashicorp/vault/issues/1310
Trace:
https://travis-ci.org/docopt/docopt.go/jobs/241851803

Coverage increased (+2.6%) to 89.904% when pulling a3199bb46d206ad2210807e23193b9e4a68c56bd on mcandre:protect-real-git-binary into 784ddc588536785e7299f7272f39101f7faccc3f on docopt:master.

Rockin'! Dropping the go get for the old vet tool helps the build out.
There's also an error with golint, which now requires Go 1.6 or later.
Source:
https://github.com/golang/lint#installation
However, Travis CI is configured to test docopt.go against Go 1.4, 1.5, and tip. Fortunately, we have several options of resolving this conflict!

Do we want to keep support for Go 1.4, and drop golint?
Do we want to keep support for Go 1.5, and try to roll back the version of golint required for testing (the parent of https://github.com/golang/lint/commit/a428635c58fe96360e83667e2e1a8343fc292bf0)?
Do we want to drop support for Go 1.4 and 1.5, and test against 1.7 and tip?

Coverage increased (+2.6%) to 89.904% when pulling 0e275d372a48861d2e6c51429ac1defb2f35d604 on mcandre:protect-real-git-binary into 784ddc588536785e7299f7272f39101f7faccc3f on docopt:master.

Coverage increased (+2.6%) to 89.904% when pulling 65b50539475def054b4a44daf2fe9dd47131471f on mcandre:protect-real-git-binary into 784ddc588536785e7299f7272f39101f7faccc3f on docopt:master.


chore: mint token details to strict mode

Summary

Please summarize your changes, describing what they are and why they were made.

...
Changelog
- Please write a list of changes

Testing
Platforms

Please select any platforms where your changes have been tested.

Desktop

[ ] MacOS
[ ] Linux
[ ] Windows

Mobile

[ ] iOS
[ ] Android

Instructions

Please describe the specific instructions, configurations, and/or test cases necessary to test and verify that your changes work as intended.

...
Checklist

Please tick the following boxes that are relevant to your changes.

[ ] I have followed the contribution guidelines for this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or modified tests that prove my changes work as intended
[ ] I have verified that new and existing unit tests pass locally with my changes
[ ] I have verified that my latest changes pass CI workflows for testing and linting
[ ] I have made corresponding changes to the documentation

I'm deleting this from inside mint-token-details.interface.ts and then approving:
export interface IEmptyMintNftDetails {
    name?: string
    totalSupply?: number
    circulatingSupply?: number
    decimals?: number
    symbol?: string
    description?: string
    url?: string
    logoUrl?: string
    aliasId?: string
}


[Feature Request] Enhance String Handling Consistency for Unicode and ASCII in KCL

Feature Request
Is your feature request related to a problem? Please describe:
Currently, string operations in KCL seem inconsistent when handling Unicode and ASCII strings. For example, the len function returns the byte length for Unicode strings but the character count for ASCII strings. Similarly, index-based operations like find and rfind appear to work with byte offsets, while slicing seems to handle code points. This inconsistency makes it challenging to work with multi-byte Unicode strings effectively.
Below are my test cases and the results in KCL v0.11.0-alpha.1:
test_unicode = lambda {
    string = "一.三"
    len = len(string)
    index = string.rindex(".")
    rindex = string.rindex(".")
    find = string.find(".")
    rfind = string.rfind(".")
    before_separator = string[0:index:]
    after_separator = string[index + 1:len:]
    print({
        len: len,
        index: index,
        rindex: rindex,
        find: find,
        rfind: rfind,
        before_separator: before_separator,
        after_separator: after_separator
    })
}

test_ascii = lambda {
    string = "1.3"
    len = len(string)
    index = string.rindex(".")
    rindex = string.rindex(".")
    find = string.find(".")
    rfind = string.rfind(".")
    before_separator = string[0:index:]
    after_separator = string[index + 1:len:]
    print({
        len: len,
        index: index,
        rindex: rindex,
        find: find,
        rfind: rfind,
        before_separator: before_separator,
        after_separator: after_separator
    })
}

Execution Results:
test_unicode: PASS (14ms)
{'len': 7, 'index': 3, 'rindex': 3, 'find': 3, 'rfind': 3, 'before_separator': '一.三', 'after_separator': ''}

test_ascii: PASS (15ms)
{'len': 3, 'index': 1, 'rindex': 1, 'find': 1, 'rfind': 1, 'before_separator': '1', 'after_separator': '3'}

Issues Observed:

len Function:

For the Unicode string "一.三", len returns 7, which seems to represent the byte length.
For the ASCII string "1.3", len returns 3, representing the character count.

Index Operations (index, rindex, find, rfind):

Both Unicode and ASCII strings return indices that appear to be based on byte offsets rather than character positions.

Describe the feature you'd like:
Introduce a built-in method (or an enhancement to existing methods) that allows consistent handling of strings, either entirely based on bytes or entirely on code points. Specifically:

A method to count characters (code points) in a string instead of bytes.
Index-based operations that work with code point positions rather than byte offsets.

Describe alternatives you've considered:

Using external libraries or utilities (kcl plugins) to preprocess strings outside KCL before working with them.
Manually handling byte offsets and converting them to code point indices, which is error-prone and inefficient.

Teachability, Documentation, Adoption, Migration Strategy:
Adding such methods would simplify handling Unicode strings for KCL users. For example:

string.char_count() could return the number of code points in a string.
Modifications to find/rfind could include an option to operate on code points.
Documentation should include examples of how these methods work with both ASCII and multi-byte Unicode strings.

By implementing this, developers would find it easier to handle strings in KCL, especially in scenarios involving mixed character sets.

According to the current implementation, the processing of Unicode and ASCII String is based on byte offset. This is also a more common practice.
For example, in rust,
fn main() {
let a: &str = "一.三";
println!("{}", a.len()); // 7
println!("{}", a.chars().count()); // 3
let c: String = "一.三".to_string();
println!("{}", c.len());   // 3
}

I think it is reasonable to add a chars() function to the string

According to the current implementation, the processing of Unicode and ASCII String is based on byte offset. This is also a more common practice. For example, in rust,
fn main() {
    let a: &str = "一.三";
    println!("{}", a.len()); // 7
    println!("{}", a.chars().count()); // 3
    let c: String = "一.三".to_string();
    println!("{}", c.len());   // 3
}

I think it is reasonable to add a chars() function to the string

Hello @He1pa
I am new to KCL and i was going through this issue and after i ran the command for .chars, it was throwing error:
attribute 'chars' not found in 'str'
Is this functionality for .chars supported in kcl or not?


No-alloc Core 3.0 schedule & no-lock IOQueue

From https://github.com/aspnet/KestrelHttpServer/pull/3093
Dependent on https://github.com/aspnet/AspNetCore/pull/3664 for IThreadPoolWorkItem https://github.com/dotnet/coreclr/pull/20387

Don’t couple these changes together. I don’t trust the lock free code yet. The other change is much simpler and we should measure them separately

FYU we plan to remove the netcoreapp2.2 and net461 frameworks from kestrel test projects. We've only just recently started our 3.0 work in earnest, so test project TFM changes have been neglected. Feel free to make that change it if will reduce the #if's you need to write.

FYI - @Tratcher is working on updating Kestrel to compile for netcoreapp3.0, which I believe should be done soon.

Replaced by https://github.com/aspnet/AspNetCore/pull/4601


Add singular resources

Closes #102
Closes #103.
I took the liberty to also refactor some minor things in InferRoute and the specs (adding a RoutesHelper to share between the different spec files), I hope you don't mind.

@paulcsmith This is ready for review now. 😃

Thank you!


Final changes to support the serialization with metapointers

This is the third and final PR related to this. It contains a refactoring of JsonSerialization that is now based on the low-level serialization functionalities. I have also split JsonSerializationTest in multiple classes.

Thank you @enikao for the review!


In some cases it not merge.

When you run the merge at this code below you will get the same code.
body {
  font-family: Arial, sans-serif;
  color: #000;
  font-size: 12px;
}
a {
  font-weight: bold;
  text-decoration: none;
}
body {
  margin: 0;
  padding: 0;
}

The output should be like this. Shouldn't it ?
body {
  font-family: Arial, sans-serif;
  color: #000;
  font-size: 12px;
  margin: 0;
  padding: 0;
}
a {
  font-weight: bold;
  text-decoration: none;
}

From the readme:

This module will attempt to merge adjacent CSS rules

Although I'm willing to look into unsafe optimisations like this one, this is expected behaviour.

I understood,
Thanks.

Could possibly add an option to disable/enable "unsafe" optimizations.


No contrast information available

In many cases, the text color info doesn't show contrast information.
Tested in Edge 102.0.1249.0 (Official build) canary (64-bit) with both the regular WCAG AA/AAA guidelines and the experimental APCA ratio.

Chrome 103.0.5054.0 (Official Build) canary (64-bit) has the same issue.
Firefox 101.0b4 (64 bits) on the other hand is showing a contrast ratio as expected for the same content

Here is one test case where contrast calculation fails, but there might be others:

Open the following URL data:text/html,<style>div::after {content: " World!";color: lightcyan;}</style><div>Hello
Select the ::after pseudo-element in the Elements panel
Click on the color swatch next to the color property in the Styles panel

The problem doesn't seem to be limited to pseudo element...
I could reproduce it on custom checkbox using a <span> within a <label>

I also tried to set the background-color on the <span> directly, without impact on the problem

Yeah, the current logic checks if the element only has 1 child node and if it is a text node. Because the <span> contains 2 child nodes (comment node and text node), then the logic fails.
I'll add your test case to the chromium bug. Thanks!

The upstream bug has been merged into this other one: https://bugs.chromium.org/p/chromium/issues/detail?id=1105775
No recent activity on it unfortunately.


Emit initial route to router subscribers

Update routing example to emit initial route to subscribers.
When you navigated to url.com/route, the router previously ignored it when linked with a component and only worked on route updates.

bors r+


proxy: audit TODO/FIXME lines. mark some for v2

Marks TODO/FIXME items that can be done after MVP/V1 status is achieved.
"v2" just means "after v1". Not at all tied to a specific version or any
order.
This cuts us down from 170 items to... 80...
Most of what was marked v2 are optimizations or require some refactoring for future features. Most of what's left are missing error handling and obvious bugs/limitations. I'll fix all of these before doing more serious edge case testing, since after looking through them a lot of these are pretty obvious.

only 63 more TODO/FIXME lines to go... not much time for code yesterday/today but at least today fixes a fairly bad bug.

42 items left. long slog is long.

31 bottles of bugs on the wall. 31 bottles of bugs. take one down, pass it around... and everyone's grossed out cuz it's bugs.


Colored output

Hi, would it be possible to, optionally via a config flag, add some colors to the output to make it easier to distinguish execution times? For example, in each of the "fastest │ slowest │ median │ mean" columns, slower times could be colored red and faster times green. I think the colored crate could be useful.

Thanks for the suggestion! I have considered coloring by column and bolding labels, but I haven't gotten around to applying any styling yet.
For this I will probably reach for @epage's anstyle crate because:

Its goals are aligned with Divan's (low overhead, few/no dependencies)
API stability
It's already a transitive dependency through clap


critical: string formatting bug leading to invalid ulog files

On master the following code:
        char b[50];
        size_t s = 5;
        snprintf(b, sizeof(b), "char[%zu] %s", s, "test");
        printf("b=%s\n", b);
        printf("char[%zu] %s\n", s, "test");
        snprintf(b, sizeof(b), "%zu", s);
        printf("b=%s\n", b);
        printf("%zu\n", s);

produces:
b=char[%zu] test
char[%zu] test
b=%zu
%zu

on NuttX. The expected output is:
b=char[5] test
char[5] test
b=5
5

As a result all (!) log files are invalid. The reason why it still works is that pyulog does not look at that field for string lengths, but FlightPlot for instance won't open the log.
%zu is both a valid C99 and C11 format specifier. It is used in the logger and at a few other places.
The commit that breaks it is the NuttX upgrade (dc10a685392f9c45e300fd76fb61a80e8669a8d7).
@davids5 can you have a look?

@bkueng - The change was introduced in the new stdio/lib_libvsprintf.c. The legacy_libvsprintf is still available but uses more space. Let me see if I can upstream a fix and backport it.

@bkueng - PR submitted upstream - I will back port if it goes in or added at as a reject if not.

Fixed in https://github.com/PX4/NuttX/pull/56


[chip-test] chip_sw_alert_handler_lpg_sleep_mode_alerts

Test point name
chip_sw_alert_handler_lpg_sleep_mode_alerts
Host side component
No response
OpenTitanTool infrastructure implemented
Yes
Contact person
@cindychip
Checklist
Please fill out this checklist as items are completed. Link to PRs and issues as appropriate.

[x] Check if existing test covers most or all of this testpoint (if so, either extend said test to cover all points, or skip the next 3 checkboxes)
[x] Device-side (C) component developed
[x] Bazel build rules developed
[x] Host-side component developed
[x] HJSON test plan updated with test name (so it shows up in the dashboard)
[ ] Test added to dvsim nightly regression (and passing at time of checking)

@bilgiday - just a quick check to see how the work is going on writing this test?

@johngt This is a work in progress. I plan to submit an initial PR today to get initial feedbacks.

@johngt, @johannheyszl Finalizing a PR for this one.

This has been implemented in https://github.com/lowRISC/opentitan/pull/16404.
We are waiting for this to pass in the nightlies now.

Hi All, good news, the test passed the latest nightlies :)
As I forget to add it into the chip_testplan.hjson yesterday, the result is shown under unmapped tests. @sriyerg just updated the hjson file with #16474. If it is okay for you, we can close the issue.

Thanks for checking - in that case this is ok to close.

Thanks @msfschaffner


[Slider] ::after:dir(...) considered incorrect in some parsers

Some strict parsing contexts will consider placing :dir after pseudo element incorrect and throw.
https://github.com/adobe/spectrum-css/blob/3c7de5e07d34ca6ca1ae873ff32f4e7a02d1f0ad/components/slider/index.css#L353-L355
See errors thrown in https://lightningcss.dev/playground/index.html#{"minify"%3Atrue%2C"customMedia"%3Atrue%2C"cssModules"%3Afalse%2C"analyzeDependencies"%3Afalse%2C"targets"%3A{"chrome"%3A6225920}%2C"include"%3A0%2C"exclude"%3A0%2C"source"%3A"div%3A%3Aafter%3Adir(ltr) {\n  color%3A red%3B\n}\n"%2C"visitorEnabled"%3Afalse%2C"visitor"%3A""%2C"unusedSymbols"%3A[]%2C"version"%3A"local"}
Not sure if this means it just gets "CSS error" (e.g. dropped) in some browsers or whether browser parsers are more lenient or something else, but it would be great if we could normalize this so that down stream tooling can more easily handle the Spectrum CSS published content.

Tracking this in Jira via CSS-751


Removed all remaining boost reference from code

Cleaned the code of all boost references
Just the build system to fix

Sorry for the noise. Seems the VC compiler is exceptionally lax and was building without issue when the GCC compiler was rightly pointing out the missing includes.


@see comments in docs should be parsed as links on the website

Is this not what happens?  See: http://www.protractortest.org/#/api?view=ElementFinder.prototype.locator

I believe they're only not links if we don't have docs for them

This is the one that I was looking at which isn't linking: http://www.protractortest.org/#/api?view=ElementFinder.prototype.evaluate

That's because the comment should say @see ElementArrayFinder.prototype.evaluate.  There is no ElementArrayFinder.evaluate.  I could have it check both or we could just fix the comment.

Ah, OK, let's just change the comment then.


Refactor GitHub Actions Workflows for Improved CI/CD Performance

Summary
This PR refactors the GitHub Actions workflows to improve the CI/CD pipeline performance for o1js by introducing parallel testing and optimized caching strategies.
All CI tests now take around 1h, down from around 3h, a 3x speed up!
Key Changes:

New Prepare Job:

Sets up the repository and Node.js environment.
Caches dependencies and build outputs (including all recursive git submodules).
Counts unit tests and calculates chunks for parallel execution.
Caches the entire repository for reuse.

Updated Build-And-Test-Server Job:

Restores repository and dependencies from cache.
Runs various integration tests and adds results to the job summary.

New Run-Unit-Tests Job:

Executes unit tests in parallel chunks
Uploads test results and adds them to the job summary.

Enhanced Build-And-Test-Web Job:

Caches Playwright browsers and runs end-to-end tests.
Uploads E2E test artifacts.

Benefits:

Faster Builds: Parallel test execution reduces overall testing time.
Efficient Caching: Speeds up jobs by reusing cached dependencies and repository states.
Enhanced Visibility: Detailed job summaries and artifact uploads provide better insights into test results.

Additional Work

Each test completes at a different time, some being more computationally expensive. It would be great to spread these out over all chunks so we can avoid hot spots where there is an imbalance of easy/difficult tests for each chunk
We could explore removing some proof tests or conditionally turn them on/off depending on changes

For some reason it still waits for status:


Tweetest prep work - Add external_custom target

I have made the update.

@smlambert This is the PR related to external_test

Will close this in favour of more progressed work in https://github.com/adoptium/aqa-tests/pull/2660 (thanks for this initial effort though!).


[core] Add hub utils

What does this PR do?
This PR adds some enhancements on peft by being able to share trained LoRA weights and configs. With this PR the API looks like the following:
from transformers import AutoModelForCausalLM
from peft import LoraConfig, LoraModel

model_id = "facebook/opt-350m"
lora_model_id = "./temp-lora"

# Create a config
config = LoraConfig(
    r=16,
    lora_alpha=32,
    target_modules=["q_proj", "v_proj"],
    lora_dropout=0.05,
    bias="none",
)
config.save_pretrained(lora_model_id)

# Load the config
config = LoraConfig.from_pretrained(lora_model_id)
model = AutoModelForCausalLM.from_pretrained(model_id)

# Load and save the model
model = LoraModel(config, model)
# save the adapters only --> here only 6MB
model.save_pretrained(lora_model_id)

# Load from saved model
model = AutoModelForCausalLM.from_pretrained(model_id)
model = LoraModel.from_pretrained(model, lora_model_id)

This PR adds:

from_pretrained support for xxConfig and LoraModel
save_pretrained support for xxConfig and LoraModel

TODOs:

[x] push_to_hub support
[x] add tests
[x] add nice docstrings

cc @pacman100

@younesbelkada would it make more sense to retrieve the base model from the LoRA model id?
Something like so?
from huggingface_hub.repocard import RepoCard

card = RepoCard.load(lora_model_id)
base_model_id = card.data.to_dict()["base_model"]

model = AutoModelForCausalLM.from_pretrained(base_model_id)
model = LoraModel.from_pretrained(model, lora_model_id)

A full-fledged example is here: https://huggingface.co/docs/diffusers/main/en/training/lora

Yes makes totally sense, will work on that!

I have now a working v1 that includes also the feature you have asked @sayakpaul so that it can be adapted / used in diffusers.
Now you can safely push / save adapters locally and / or the Hub. You can also push adapter_config easily on the Hub for all supported configurations. However, I tried to have a look if I can refactor the code to support from_pretrained & push_to_hub  for all adapter models but this seemed to imply a lot of code changes that I didn't wanted to address now and prefer to let them in a follow up PR.
The latest changes adds also nice tests, for config and adapter models
Here is an example of pushed adapter weights of facebook/opt-350m that I have pushed on the Hub: https://huggingface.co/ybelkada/test-opt-lora/tree/main and you can load within this PR with the following:
from transformers import AutoModelForCausalLM
from peft import LoraConfig, LoraModel

from huggingface_hub.repocard import RepoCard

lora_model_id = "ybelkada/test-opt-lora"
card = RepoCard.load(lora_model_id)
model_id = card.data.to_dict()["base_model"]

# Load the config & model
config = LoraConfig.from_pretrained(lora_model_id)
model = AutoModelForCausalLM.from_pretrained(model_id)

# Load the Lora model
model = LoraModel.from_pretrained(model, lora_model_id)

Love it. Thanks you, Younes!

@younesbelkada I spun up this Colab Notebook quickly to showcase LoRA (from PEFT) for image classification and wow: https://colab.research.google.com/drive/1GtKXiVyINz2rRnd5FSMh2WnTjt7nOTEn?usp=sharing ❤
I guess after this PR is merged, we should incorporate Hub-related utilities in the Notebook. WDYT?
Thanks to @pacman100 for his guidance and help.

Thanks a lot for sharing the notebook @sayakpaul !
Yes let's wait for this PR to be merged and we can add how to share/load lora weights on the Hub to the notebook!

Cool, I am looking forward to it. Next, I will try SegFormer.
My plan is to come up with the faithful benchmarks that users can refer to while using PEFT for computer vision to really see the benefits.

Hello @younesbelkada, Thanks a lot for adding hf hub utils and test 🤗. Few general comments:

Instead of having a base model name in the README, let's add base_model_name_or_path to the PeftConfig class. So, the saved peft_config can look like this:

{
  "base_model_name_or_path": "facebook/opt-350m",
  "bias": "none",
  "enable_lora": null,
  "fan_in_fan_out": false,
  "inference_mode": false,
  "lora_alpha": 32,
  "lora_dropout": 0.05,
  "merge_weights": false,
  "peft_type": "LORA",
  "r": 16,
  "target_modules": [
    "q_proj",
    "v_proj"
  ],
  "task_type": "SEQ_CLS"
}

With this one can load the model:
# Load the config & model
config = LoraConfig.from_pretrained(lora_model_id)
model = AutoModelForCausalLM.from_pretrained(config.base_model_name_or_path)

# Load the Lora model
model = LoraModel.from_pretrained(model, lora_model_id)

I have tried extending this PR to add save and load utils for all Peft model tasks covering available adapters in this PR: #43.
Could you please look at that, port relevant parts and make necessary updates? This would enable support for all adapters, which would be great. Below is an example of the prefix-tuning PEFT method on the seq_cls task:

Saving
# save the config and model
peft_model_id = "./temp-peft-prefix-tuning"
model.save_pretrained(peft_model_id)

Loading
# Load the config & model
from peft import PeftModel, PeftConfig
config = PeftConfig.from_pretrained(peft_model_id)
model = AutoModelForSequenceClassification.from_pretrained(config.base_model_name_or_path,  return_dict=True)

# Load the Lora model
model = PeftModel.from_pretrained(model, peft_model_id)

Could you please run make style and make quality to fix code style and quality?

Left a few other suggestions and comments.

Thanks a lot for the feedback @pacman100 !
I should have addressed your comments now :D
However regarding tests, they are failing for other peft methods since I am not aware of the canonical way of loading a PeftModel using these classes. Let me know what I can do next!


setup docker for raspberry pi

https://phoenixnap.com/kb/docker-on-raspberry-pi

curl -fsSL https://get.docker.com -o get-docker.sh

sudo sh get-docker.sh

sudo usermod -aG docker pi

docker version
throwing error:
ERROR: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/info": dial unix /var/run/docker.sock: connect: permission denied
errors pretty printing info

docker info
throwing error:
ERROR: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/info": dial unix /var/run/docker.sock: connect: permission denied
errors pretty printing info

5.5 to resolve errors above:
sudo chmod 666 /var/run/docker.sock

docker run hello-world

docker run cjkrolak/thermostatsupervisor exited with this error:
Status: Downloaded newer image for cjkrolak/thermostatsupervisor:latest
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm/v6) and no specific platform was requested
standard_init_linux.go:228: exec user process caused: exec format error

build failing with new yml updates on develop, needs investigation:
Run docker buildx build . --push \ --tag thermostatsupervisor:$(date +%s) \ --platform linux/amd64,linux/arm/v7,linux/arm64
error: "docker buildx build" requires exactly 1 argument.
See 'docker buildx build --help'.
Usage:  docker buildx build [OPTIONS] PATH | URL | -
Start a build
Error: Process completed with exit code 1.

even after adding this command "run docker buildx create –-use"
still getting this error message:
Run docker buildx build --platform linux/amd64,linux/arm/v6,linux/arm/v7,linux/arm64 --tag ***/thermostatsupervisor:latest --push .
error: multiple platforms feature is currently not supported for docker driver. Please switch to a different driver (eg. "docker buildx create --use")
Error: Process completed with exit code 1.

multi-platform fixes checked into develop and main on 2/5/22, Dockerfile and docker-image.yml required updates.  Now getting permission error when running the image on pi4, opened #455 to address this issue


fix import

robotstxt.go renamed to robotstxt-go now
https://github.com/temoto/robotstxt-go

Thanks!


No-indent commenting of code

Currently, Ctrl+/ inserts additional indent into commented out code and it seems there's no way to disable that behavior. I'd appreciate an option allowing to comment out the code starting from the first column, so instead of this:
    //function foo() {
    //    echo 'Foo';
    //}

to have this:
//    function foo() {
//        echo 'Foo';
//    }

It could be as simple as toggle switch (e.g. disable indent in commented out code) or (not necessarily) more advanced, where the comment's indent is taken from current cursor position, if it's between first column and first printable character in cursor's line.

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


opts vs. options

The true name of the options dictionary is opts but it is referred to as options in the Readme.

Yeah, this is due to a discrepancy in the naming between the Lua and the Python wrapper. It may be hard to fix now without breaking things in people's code?

Would it be worth overloading with options for the sake of consistency (and documentation), and gradually deprecating the opts version? It might be a heavy change looking at the code, but better now than later.

IMO, we should actually change options to opts :)

Either sound good as long as they're the same

I'd be down to change that on the Lua side - it doesn't look as heavily used by Github search. Or even just the docs.

moved from options to opts in 135525a224fe4b7bf859768517ef7e9344c0b570


License compatibility

In OpenBazaar we use the MIT license, and we also use pyelliptic. However, I believe this use may be incompatible with our licenses.
Would you please give us your opinion on how you think we should solve this licensing incompatibility?
As pyelliptic is a library, would it be reasonable to ask to switch to the LGPL so that it can be used as an external library in projects such as OpenBazaar?
Thank you very much!

@Kagami thanks, I'll fix that.


Update attribution URL to point to correct page on github

Link was broken when project moved to osmlab org

Thanks Jesse!


cudaPackages.nccl: 2.21.5-1 -> 2.23.4-1

Things done
(will get back to this in 24h, draft for now.)

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

dupe of bot: https://github.com/NixOS/nixpkgs/pull/322260


[DF-619] Added Related Resources Column

/claim #619
/fixes #619
https://github.com/dittofeed/dittofeed/assets/64700961/98954be4-2f2d-48f7-bd7f-ac3feb3b2302

Can you post a recording showing a BadWorkspaceConfiguration event in the table specifically? You can trigger this by using a template that references a user property which is not defined on the user. Thank you!

https://github.com/dittofeed/dittofeed/assets/64700961/14f0a0f4-418b-49ec-b457-9a3eb7041ff1


[PowerRename] Empty Extension renaming

Summary of the new feature/enhancement

i was trying to rename a bunch of file with an empty extension but apparently PowerRename couldn't rename extension type if the file doesn't have one
With RegEx

Without RegEx
because there's no " . " in the file name there's no change

Proposed technical implementation details (optional)
i was expecting result something like this

Hi @GagahGK
try selecting the 'Match All Occurrences` flag.

it works now
thanks 😁


Fix {name} to v2 format ${{name}}

Description
Fix {name} to v2 format ${{name}}
spec: https://github.com/Azure/azureml_run_specification/blob/master/specs/outputs.md
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-ai-ml


LoginAsync Method with parameter useSingleSignOn and default browser stays open using uriScheme [UWP]

@dhei Man I saw you tutorial at comment #351, let me tell you that using uriScheme works for me, but still I cant make it work using the overload method with useSingleSignOn it send me to this place:

I'm using as a provider facebook authentication, an even though i had made it work with uriScheme, how can i set my azure mobile app or my client to make this work with useSingleSignOn boolean.
because If i go back to v3.1.0 it works great, but I think its important to update always to last version, so hopefully you guys can show me a tutorial or explain me if this still on development, because I cant find any sense to that overloaded method.
It feels like a regression in UX to me honestly. also if I use uriScheme and I'm refreshing my token or login in for the very first time it open default browser after loginasync and stays open, what happened there??
I'm using UWP, thats the actual ugly experience there. this v4.0.0 or v4.0.1 i think was to hasty, we werent rdy to it yet.

I have the same problem.
UWP app (targeting 1703 Creators update, Windows 10.0.15063). Upgraded the package to v4.0.1 (v3.1.0 worked great). Now the LoginAsync extension method with useSingleSignOn = true leaves the login window open. If I close it, the method throws exception (HTTP code 403) - because it thinks I have cancelled the authentication.
I'm using this extensions method with Microsoft account provider:

Microsoft.WindowsAzure.MobileServices.SingleSignOnExtensions.LoginAsync(this IMobileServiceClient client, MobileServiceAuthenticationProvider provider, bool useSingleSignOn)

Same problem hear too.

With this steps works for me:
example : https://workplace.azurewebsites.net
{url_scheme_of_your_app}  => workplace
1 Azure > .Authentication / Authorization >>  ALLOWED EXTERNAL REDIRECT URLS
{url_scheme_of_your_app}://easyauth.callback

replace the OnNavigatedTo()  the YourPage.Xml
protected override async void OnNavigatedTo(NavigationEventArgs e)
{
if (e.Parameter is Uri)
{
App.MobileService.ResumeWithURL(e.Parameter as Uri);
}
}

3 Add the following code snippet to the App.xaml.cs
protected override void OnActivated(IActivatedEventArgs args)
{
if (args.Kind == ActivationKind.Protocol)
{
ProtocolActivatedEventArgs protocolArgs = args as ProtocolActivatedEventArgs;
Frame content = Window.Current.Content as Frame;
if (content.Content.GetType() == typeof(YourPage))
{
content.Navigate(typeof(YourPage), protocolArgs.Uri);
}
}
Window.Current.Activate();
base.OnActivated(args);
}

Method AuthenticateAsync

user = await App.MobileService
.LoginAsync(MobileServiceAuthenticationProvider.Facebook, {url_scheme_of_your_app}.);

Package.appxmanifest file

Navigate to Declarations, in Available Declarations dropdown list, select Protocol and click Add button. Now configure the Properties of the Protocol declaration. In Display name, add the name you wish to display to users of your application. In Name, {url_scheme_of_your_app}.

@Quico20 Thanks for using Azure Mobile Apps. Were you able to resolve this issue based on the discussion above? Please read the Readme section on this repo which talks about the future of Azure Mobile Apps. I'll close this issue for now, but feel free to ask us questions if you have any. Thanks!


[ENG-10922][eas-json] add new Xcode 15.1 image to eas.schema.json

Why
We are adding Xcode 15.1 image
How
Add new Xcode 15.1 image to eas.schema.json
Test Plan
Tests

/changelog-entry chore Add new Xcode 15.1 image to eas.schema.json

Changes look good to me. @brentvatne, do we need to post a changelog about upcoming default change from macos-ventura-13.4-xcode-14.3.1 to macos-ventura-13.6-xcode-15.0?

@szdziedzic and i discussed this a bit today. were you referring to the "explicit default" case (where someone specifies "image": "default") here?


align permission structure with model urls

Issue: usage of permissions unclear
the permission model has "url" as input field. when using I would expect it to mimic the url structure of the models. (i.e. "/Role/all" or "/Role/edit"). Instead it performs checks for a permission like "Roleall" or "Roleedit" which isnt readable or intuitive.
Change
the urls for those checks have been modified to mimic a readable structure:
/[Model]/[action]
Permission usage

Create permissions like the example below via the permission CRUD controller:
url: /Role/all
description: View Roles
Create new desired role
Assign permission to new role via role CRUD controller

Thank you for great work , please send a pull request to github.com/laravelpanel/docs for changes in documents

i will do that. thank you for the quick merge as always.


No way to add optional arguments to build command

I've had a go at utilizing this for building tensorflow serving, I can build and run okay but I cannot debug as ill need to add the --compilation_mode=dbg flag to the bazel build string. is there a way to do this? Short of forking and appending in BAZEL Command?

You can also set it to your ~/.bazelrc but definitely having a way to set it inside eclipse would be good.

That's a good point above; I don't know why I didn't think of that as I'd seen it used elsewhere...
Definitely would be nice to have an option though, especially since the infrastructure seems there... I'll give the ~/.bazelrc a go.


drivers: intc: plic: remove incorrect arch_proc_id() usage

The arch_proc_id() returns the hartid of a CPU, which may not start from zero. The way that it's used as an index to access save_irq[] array is wrong, use arch_curr_cpu()->id instead.

A search for arch_proc_id() reveals more potential incorrect usage of the API, i.e.:
https://github.com/zephyrproject-rtos/zephyr/blob/c0a0e6a3887c53e5519ae5b30352b39cf7e9288f/soc/intel/intel_adsp/ace/multiprocessing.c#L222-L235
If the arch_proc_id() returns non-sequential id that doesn't start from 0, some of the core might be skipped in the for-loop.

https://github.com/zephyrproject-rtos/zephyr/blob/c0a0e6a3887c53e5519ae5b30352b39cf7e9288f/soc/intel/intel_adsp/ace/power.c#L129
https://github.com/zephyrproject-rtos/zephyr/blob/c0a0e6a3887c53e5519ae5b30352b39cf7e9288f/soc/intel/intel_adsp/ace/power.c#L162-L181
If the arch_proc_id() returns a unique id like 128, we could have an out-of-bound access above..


CSV-252: Migration to JUnit Jupiter

This PR upgrades the project's testing framework from JUnit 4.12 to the modern JUnit Jupiter 5.5.4.
Since JUnit 5 Jupiter is not backwards compatible to JUnit 4.x (or even JUnit Vintage), this patch is a bit large, even though a lot of the changes are merely cosmetic (such as changing the argument order, see details below). In order to make the reviewer's task as easy as possible, this PR does not presume to use JUnit Jupiter's best practices and all its new functionality, but only to migrate the existing tests with as little change as possible. Following PRs may want to improve the tests by using some of JUnit Jupiter's new features.
This PR includes the following changes:

Maven dependency changes:

junit:junit was replaced with org.junit.jupiter:junit-jupiter.
org.hamcrest:hamcrest was introduced as an explicit dependency, since the project uses Hamcrest, and JUnit Jupiter does not bundle Hamcrest, unlike JUnit 4.x.
The Mockito dependency was upgraded from org.mockito.mockito-all:1.10.19 to org.mockito:mockito-core:3.1.0, which supports JUnit Jupiter.

Annotations:

org.junit.jupiter.api.Test was used as a drop in replacement for org.juit.Test without arguments. See 3.ii. for handling of @Test annotations with an expected argument.
org.junit.jupiter.api.BeforeEach was used as a drop in replacement for org.junit.Before.
org.junit.jupiter.api.BeforeAll was used as a drop in replacement for org.junit.BeforeClass.
org.junit.jupiter.api.Disabled was used as a drop in replacement for org.junit.Ignore.

Assertions:

org.junit.jupiter.api.Assertions' methods were used as drop in replacements for org.junit.Assert's methods with the same name in the simple case of an assertion without a message. In the case of an assertion with a message, org.junit.jupiter.api.Assertions' methods were used, but the argument order was changed - Assert's methods take the message as the first argument, while Assertions' methods take the message as the last argument.
org.junit.jupiter.api.Assertions#assertThrows was used to assert that a specific exception was thrown instead of an org.junit.Test annotation with an expected argument. This technique has a couple of side bonuses. First, it makes the tests slightly stricter, as now they can assert the exception was thrown from a specific line and prevent false positives where the test's "set-up" code accidentally threw that exception. Second, it clarifies that some of the test code is unreachable (as a previous line already throws an exception), and can safely be removed in order to clean up the test. The throws clauses of these methods were cleaned up from exceptions that can no longer be thrown in order to avoid compilation warnings.
org.hamcrest.MatcherAssert#assertThat was used as a drop in replacement for org.junit.Assert#assertThat.
org.junit.jupiter.api.Assertions#assertNull was used as a drop in replacement for junit.framework.TestCase#assertNull.

Specific Changes:

CSVFileParserTest was rewritten with JUnit Jupiter's org.junit.jupiter.api.ParameterizedTest.  Unlike JUnit 4's org.junit.runners.Parameterized, it cannot be used to inject arguments to a test's construct, and so the test can't be stateful. Instead, it was rewritten so every test receives the file as a parameter, and opens a reader on it itself. As a side bonus, this design makes it easier to close the reader and avoid leaving open file descriptors like the original test did.

Closes CSV-252

Coverage remained the same at 92.928% when pulling f6f399c02519ba7d0f4ef3c456570ed6afb08a9e on mureinik:CSV-252-jupiter-upgrade into 6aa17567501c94e2ed65dc0c2f2ff3c01e534bd5 on apache:master.

@mureinik
Thank you for your contribution to modernize Apache Commons CSV! :-)
Gary


Hiring independent contractors

Document documents for hiring independent contractors ("Individual Service Providers". Some places to start:

https://www.finance.upenn.edu/payments-disbursing-funds/paying-independent-contractors/
HR contacts by school for ISPs: https://www.hr.upenn.edu/policies-and-procedures/processes-and-procedures/service-provider-classification/hr-contacts-for-individual-service-providers
Classification process: https://www.hr.upenn.edu/policies-and-procedures/processes-and-procedures/service-provider-classification
Training on ISPs, slides 17 - 20 are relevant: https://www.hr.upenn.edu/docs/default-source/service-provider-classification/classifying-individual-service-providers-training-pp.pdf?sfvrsn=ec858756_64
Procedural guide: https://www.hr.upenn.edu/docs/default-source/service-provider-classification/procedural-guide-for-ic-and-le.pdf?sfvrsn=e16e8756_38
BEN/Penn Marketplace: https://cms.business-services.upenn.edu/purchasing/images/stories/pdfs/business entity - independent contractor resource guide 3.26.18.pdf

@shapeseas what's pending here? Does this stuff need to be permanently documented here in some way?

Nothing pending - feel free to close. There may be some room for
documentation but likely would sit in CSSLabOps repository.
On Thursday, June 16, 2022, Mark Whiting @.***> wrote:

@shapeseas
https://urldefense.com/v3/__https://github.com/shapeseas__;!!IBzWLUs!WzEEaPLFTSwYfsMjcaX1vmaYzlQ7EPwZD_mfd82snLtpnSjx005KgQl_PxRz5kInRK_51DR3ymJE_-cX0j-xxRYDRGQ$
what's pending here? Does this stuff need to be permanently documented here
in some way?
—
Reply to this email directly, view it on GitHub
https://urldefense.com/v3/__https://github.com/Watts-Lab/handbook/issues/3*issuecomment-1157961091__;Iw!!IBzWLUs!WzEEaPLFTSwYfsMjcaX1vmaYzlQ7EPwZD_mfd82snLtpnSjx005KgQl_PxRz5kInRK_51DR3ymJE_-cX0j-xq2jbfwc$,
or unsubscribe
https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/APA2AIDTBOPZC3C7BHTV5QLVPNR7HANCNFSM5HS4VYFQ__;!!IBzWLUs!WzEEaPLFTSwYfsMjcaX1vmaYzlQ7EPwZD_mfd82snLtpnSjx005KgQl_PxRz5kInRK_51DR3ymJE_-cX0j-xGUOwefs$
.
You are receiving this because you were mentioned.Message ID:
@.***>

Got it, should we move these notes there?


Used raylib enums instead of i32

I've covered the ones that I use + whatever I found around it. It is not extensive (I've probably missed some cases) but it is a step in the right direction.
Also, I added FontAtlasPackMethod, which doesn't explicitly exist in raylib, but it is how it is used in raylib.

This should be integrated with fix_enums in generate_functions.py

There are several issues with this PR; it doesn't integrate with the generator script, I don't like the int/enum casts in member functions and you should add the FontAtlasPackMethod to raylib before it can be in this binding. I'm closing the PR, but I will add your changes alongside other enum improvements relating to #93


latest.py sometimes adds empty lines in frontmatter

latest.py sometimes adds empty lines in frontmatter when it is executed. And example of this can be found on https://github.com/endoflife-date/endoflife.date/pull/2042/files, for ios.md or ipados.md.
No additional empty lines should be added by the script: we should try to fix it.

Hope the issue is not in the library used for updating the frontmatter.

@captn3m0, do you know what cause empty lines to be added to the frontmatter ?

It is a quirk of the library. If the last item in the frontmatter is a list (which our releases object is in the case here), the library we use will add a newline at the end of the output.
Fixed with a workaround in #2056

Great, thanks.


Assigning a new node to an existing tree

I feel like I'm missing something but this is the best I could come up with
a05["natre"] = datatree.DataTree.from_dict({"natre": xarray_dataset})["natre"]

Is this right?

You should be able to just do
a05["natre"] = DataTree(xarray_dataset)
(Also are you using the packaged version or main? Because I changed alot just a couple of days ago that I still need to release, see #76)

I'm using main, because I didn't read the docs :). I only look for badges in READMEs nowadays haha.

Okay well let me know if that works!

That works thanks.


db2: colums is always created with Not Null checked [D4]

System information:

Operating system (distribution) and version win 10 x64

DBeaver version 6.2.3

Connection specification:
- Database name and version db2 LUW

Describe the problem you're observing:
All created columns has Not Null option enabled, it is causes error when trying to save created column
Steps to reproduce, if exist:
1, Open Table
2. Create Column -> Check enabled options (Not null is checked)

Created by TestQuality - Linked to TestQuality.com defect D4. Do not remove or edit. D4

Fixed

verified


Over usage same web data

When I request the page with Copilot, it does the same page data over and over again, just like it does with web-search, when it should do it once.

Four citations from the same source are displaying because Page Assist uses a technique that splits large amounts of data into smaller chunks for RAG. The citations are currently set to open in a new tab, but I will update this so that clicking them opens a modal showing the parts sent to the LLM.


[1.4.x] Bump semanticdb version to 4.4.0

Fixes #6144
Bump semanticdb to 4.4.0 since it is the only one compatible with 2.13.4 (https://mvnrepository.com/artifact/org.scalameta/semanticdb-scalac). It is also compatible with all previous versions:

2.13.4
2.13.3
2.13.2
2.13.1
2.13.0
2.12.12
2.12.11
2.12.10
2.12.9
2.12.8
2.11.12

@adpi2 Thanks. Could you send a backport PR against 1.4.x as well plz?

@eed3si9n this one is merged into 1.4.x. Do you want me to open a PR against develop or maybe we just need to merge 1.4.x into develop?

@adpi2 There's been a few back ports already, but whatever works is fine.


Upgrade dependencies in at_client_mobile, test and publish

[x] Upgrade dependencies in at_client_mobile
[x] Test the updated dependencies with the apps
[x] Publish the package once testing is good

The following branch has the updated dependency branch

published at_client_mobile: 3.2.10


Enable Component parameter delegates to not require @() for coloring at design time.

The core issue is that the Razor parser splits attribute values based on whitespace. Therefore, when it encounters @onclick="() => Foo()" it breaks it into three different tokens based on the spaces involved. This separation results in multiple adjacent classified spans for C# which is currently unsupported by WTE due to multiple seams overlapping. All that being said we have the opportunity to be smarter when generating attribute values that we feel can be simplified or collapsed; because of this in this PR I changed the TagHelperBlockRewriter phase to understand "simple" collapsible blocks and to then collapse them. In the future a goal would be to take a collapsing approach to all potential attributes and then to re-inspect each token individually at higher layers in order to decouple our TagHelper phases from what the parser initially parses.
Added an integration and parser test to validate the new functionality. Most of the testing is from the fact that no other tests had to change because of this (it doesn't break anything).
Added a new SyntaxNode method GetTokens that flattens a node into only its token representation.

aspnet/AspNetCore#11826

@aspnet/build it looks like the CI has completed but the reporting from azure devops to GitHub is broken? Is this a known issue?

Is this a known issue?

I haven't heard anything. But, transient problems like this do happen occasionally. @MattGal?

BTW, you can still push this commit @NTaylorMullen

@dougbu this is a communication burp between Azure DevOps and Github, and are usually fairly rare (like < once / day).  Given both pieces have their own concept of throttling / tarpitting, it may be related to this;  If we can gather enough instances we may be able to get AzDO to investigate, until then I suggest just restarting checks unnecessarily or merging after checking in AzDO.


uv venv's -p help has incorrectly rendered list

λ ~ :: uv help venv
Create a virtual environment

Usage: uv venv [OPTIONS] [NAME]

Arguments:
  [NAME]
          The path to the virtual environment to create

          [default: .venv]

Options:
  -p, --python <PYTHON>
          The Python interpreter to use for the virtual environment.

          Supported formats: * `-p 3.10` searches for an installed Python 3.10 (`py --list-paths` on Windows, `python3.10` on Linux/Mac). Specifying a patch version is not supported. * `-p python3.10` or `-p python.exe` looks for a binary in `PATH`. * `-p /home/ferris/.local/bin/python3.10` uses this exact Python.

          Note that this is different from `--python-version` in `pip compile`, which takes `3.10` or `3.10.13` and doesn't look for a Python interpreter on disk.

I'd expect it to be:
λ ~ :: uv help venv
Create a virtual environment

Usage: uv venv [OPTIONS] [NAME]

Arguments:
  [NAME]
          The path to the virtual environment to create

          [default: .venv]

Options:
  -p, --python <PYTHON>
          The Python interpreter to use for the virtual environment.

          Supported formats:
			* `-p 3.10` searches for an installed Python 3.10 (`py --list-paths` on Windows, `python3.10` on Linux/Mac). Specifying a patch version is not supported.
			* `-p python3.10` or `-p python.exe` looks for a binary in `PATH`.
			* `-p /home/ferris/.local/bin/python3.10` uses this exact Python.

          Note that this is different from `--python-version` in `pip compile`, which takes `3.10` or `3.10.13` and doesn't look for a Python interpreter on disk.

Oops, thanks.

Thanks! I'm not sure how to fix this rendering. We'll need to look into Clap's documentation.

You can try #[clap(verbatim_doc_comment)] on the option. But it turns off some other comment transformations