versioning issue

Description
please remove this versioning as it becomes too tough to install right package for many nugest as one is dependant on another

I'm not sure what you're asking, sorry.

we now need to use specific version of llamasharp for specific models.
so we cant use updated packages with some packages.
So try making normal versioning which can help tto always use updated packages

We do have fairly up to date integrations for kernel memory, if there's a specific issue with them please report it! (I'm not familiar with handlebars planner, looks like it's part of semantic kernel? If so, we have an integration with that too).

WHY DOES IT FAILS FOR HANDLEBARS PLANNING

WHY DOES IT FAILS FOR HANDLEBARS PLANNING

You can't expect a response with this tone of voice.
This is an open source project.
If you want something fixed maybe pay for it?

Or contribute a fix of course ;)
Anyway I'm going to close this issue for now. @Barshan-Mandal if you want to open up an issue describing the exact issue, with details to reproduce please go ahead. But keep in mind this is an open source project, and the people who write the code are the people who want that feature to work.

WHY DOES IT FAILS FOR HANDLEBARS PLANNING

You can't expect a response with this tone of voice. This is an open source project. If you want something fixed maybe pay for it?

where should i pay it?.my response was not harse

WHY DOES IT FAILS FOR HANDLEBARS PLANNING

You can't expect a response with this tone of voice. This is an open source project. If you want something fixed maybe pay for it?

where should i pay it?.my response was not harse

You can fix it yourself if you have the skills.
If you don't and you really want this addressed, then you can hire a developer.
Take a look at Fiverr, you can hire freelance developers there.

To be clear, payment isn't required to take part in this project! But if you're not planning to write the code yourself, you need to provide a clear issue report to help any kind volunteers who want to fix the issue!


TPU models

How do you install the Custom Models for TPU?  The Coral Model doesn't have a custom model folder and I don't think it uses YOLO as far as I'm aware at least.

I'm also interested
I see the custom yolov8 model for Coral in the code. It's already been released?

I have not had any free time to work on a new module that will use my custom models, hopefully next month I will find some time

I saw that the from CodeProject it supports Yolov5 and Yolov8, would using the Yolov8 models in this case work for the Coral TPU?

Does anyone find a way to use these models?

Duplicate of #5 I think.

Thanks for the work @MikeLud     This is great stuff, I think, if I could get it loaded.  I've copied the Coral models to the codeproject assets directory, and I think I can get the YoloV5 and Yolov8 models running.  But for the life of me I cannot get the custom_models directory or the ipcam-general model loaded.   Any clue or instructions?
Jeff

Its been a while has this been implemented yet? Trying to just use the combined model to detect animals.

Anyone figure out how to add the custom models yet?

Another interested party here.
How do we use the custom yolov8 models?

@MikeLud sry for tagging, any way we could use your custom-models in cpai with coral?


Lock version of n3 to <1.9.0

There's no clear changelog, but there were changes that at least
affected our tests (see https://github.com/inrupt/solid-client-js/pull/918#issuecomment-800901838), and also seem to result in no longer being able to generate the correct Turtle from a SolidDataset's ChangeLog. (It results in a string consisting of just a single period (.).)
This PR fixes #957.

[ ] I've added a unit test to test for potential regressions of this bug. (Probably N/A - this might be a bug in N3 directly, but will have to investigate that.)
[x] The changelog has been updated, if applicable.
[x] Commits in this PR are minimal and have descriptive commit messages.

CI builds being annoying all of a sudden - dependencies should be the same, but for some reason all of a sudden compilation fails in the browser-based end-to-end tests.
Either way, here's a confirmation that this does indeed fix the reported issue: https://forum.solidproject.org/t/curious-400-error-when-removing-using-inrupt/4163/6?u=vincent


Rocket.chat integration

Rocket chat integration using fetch to send post request to a rocket.chat webhook
The dockerfile was improved to make it faster to reload on modifications (caching npm install), going from 5minutes to 10 seconds.

the docker file have a problem at the run-srcript step at first build


Configure the MetricsFeature through application.properties

Currently to enable metrics for quarkus-cxf it is required to use the specific feature module quarkus-cxf-rt-features-metrics and configure reference a framework class for each client or endpoint that wants to enable it.
quarkus.cxf.client.MYCLIENT.features=io.quarkiverse.cxf.metrics.QuarkusCxfMetricsFeature

Other libraries (Hibernate, Log, Scheduler, GraphQL, etc...) typically have a boolean parameter like
quarkus.EXTENSION.metrics.enabled
Would be great to have a similar parameter for quarkus-cxf. This would reduce repetitive boilerplate in the application.properties and make it very straightforward to add. Similar treatment to what was done for logging recently in https://github.com/quarkiverse/quarkus-cxf/pull/1102
Could be global as quarkus.cxf.metrics.enabled
Or separated for client and endpoint quarkus.cxf.client.metrics.enabled and quarkus.cxf.endpoint.metrics.enabled if needed.

Sounds great. Thanks for the change!


Performance degradation when using combine_reducer and state consists of objects that implement __eq__

The combine function is causing a huge performance degradation by using the equality operator != instead of is not.
https://github.com/usrlocalben/pydux/blob/943ca1c75357b9289f55f17ff2d997a66a3313a4/pydux/combine_reducers.py#L77-L78
This causes the whole state to be compared on each action that reaches the reducer, even if the actions are not handled in any reducer at all.
When the state consists of dictionaries, is not that obvious because dictionary comparison is very fast.
When the state consists of 'normal' class objects its also fast because __eq__ falls back to comparing identity using is.
When we modeled our state using pydantic it converts the objects to dicts first to compare for equality when using != which caused a significant performance impact.
We simply fixed it using is  not in the combine function.
https://github.com/zuhause-plattform/pydux/commit/f5e2bce948e296868015795d0ec67b5dbdee73b4

If a reducer gives a new object instance (dict or otherwise) but has the same value this should fail. i.e. foo is not bar, yet foo == bar.
You are right, that reducers() that don't handle an action generally follow the pattern of returning the input (reference) so those results would pass the is test. However, it's not a requirement that reducers do this.
The following expr will short-circuit such that you get the is optimization you want without breaking the general value-semantic case.
has_changed = has_changed or not (next_state_for_key is previous_state_for_key or next_state_for_key == previous_state_for_key)
In [62]: xa = {'foo': 'bar'}
In [63]: xb = xa
In [64]: not (xa is xb or xa == xb)
Out[64]: False

In [65]: xa = {'foo': 'bar'}
In [66]: xb = {'foo': 'bar'}
In [67]: xa is xb
Out[67]: False
In [68]: not (xa is xb or xa == xb)
Out[68]: False

You are right, that reducers() that don't handle an action generally follow the pattern of returning the input (reference) so those results would pass the is test. However, it's not a requirement that reducers do this.

I didn't know that it was expected behavior to get the old reference back if a new state was returned but the attributes had the same values. IMHO its a little bit counter-intuitive, especially because that behavior is only introduced by the combine_reducer function. The behavior is not present when using only one reducer, or am I missing something?
Anyway I like your optimization. This will negate most of the negative performance impact.
And thanks for your quick response 👍

The topic kept being stuck in my head, because I couldn't find out the reasoning behind this behavior.
I investigated a little bit more and now I'm convinced that comparing for identity is actually the intended behavior of the original redux implementation in js and using the equality operator might be a mistake that happened while porting to python.
Looking at the implemetation of the reduxjs repo the key line is
hasChanged = hasChanged || nextStateForKey !== previousStateForKey
if we test you example above in a javascript environment using !== we can see, that there is no equality of the two objects even if the attributes are the same.
❯ node
> xa = {'foo': 'bar'}
{ foo: 'bar' }
> xb = {'foo': 'bar'}
{ foo: 'bar' }
> xa !== xb
true

AFAIK there is no way to implement an equality function like we can with __eq__ in python, so an objects is only equal to itself in js.
(Disclaimer: I might be wrong Im not a js programmer, thats just what I found out)

You have persuaded me.
Do you want to bring a PR?

Will happily prepare a PR later.
One thing that I want to note, is that, there are unfortunately some cases where using is won't yield the same results as in JS:
❯ node
> a = 10e10
100000000000
> b = 10e10
100000000000
> a === b
true
>

while
❯ python3
>>> a = 10e10
>>> b = 10e10
>>> a == b
True
>>> a is b
False
>>>

I think its a kind of rare case, because most people will use objects to hold state, but if you would just use primitive number than it will break with numbers > 256
>>> a = 256
>>> b = 256
>>> a is b
True
>>> b = 257
>>> a = 257
>>> a is b
False
>>>

Interesting.
In the case that anyone out there is using this lib and depends (perhaps unknowingly) on the == behavior, it could still be preferred to implement it as I suggested above, using a is b or a == b. Do you see any downside?

Yeah i guess that would be the simplest solution. One could try to exactly mimic the JS comparison, but then you had to do some isinstance checks. Don't know if that is feasible.
Another option would be to add an additional optional keyword argument to the combine_reducers function, like compare_identity_only or something like that, but I don't know if you would consider this elegant.


Add logic so that the professor's email is stored for each section that a user is subscribed to.

Parent Issue: #106
Hours: 3 hours

Also: Figure out where it should be stored so as to be accessible to the user locally.

I'm thinking that every time a user adds a course section to their courseArray, an update should be made under the path /professor/[professor email]/[course section ]:(full course section path from root) this way, when a user logs in, we can just search to see if the path /professor/[user email] exists. If it does, then that user is a professor that teaches several courses with subscribers. We would then only need to get each course section object under  /professor/[user email]/ in order to get the path to push our new white-listed emails to.

Tested with a few courses, and the /professor path appeared on Firebase. This path contains the emails of several professors each of which contain multiple course sections that they teach.

Took about 3 hours do to a small bug I couldn't resolve quickly.


Source dependency location of composite project does not resolve correctly.

I have a test project located https://github.com/chuckb/sourcedep which attempts to build and then run a source dependency (which is a c project that uses a make plugin). While the project is downloaded, the build is not run and the resolved executable file directory contains the root project name in the path, which is not where the project is cloned.
Expected Behavior
The make task of the source dependency is executed, and then the 'command '/Users/chuck_benedict/Projects/sourcedep/.gradle/vcs-1/raspbootin_epp6hl9dpn2l5cz95jd6v3nu9/raspbootcom/raspbootcom'' is executed.
Current Behavior
The make task is not executed. The resolved task executable is instead 'command '/Users/chuck_benedict/Projects/sourcedep/.gradle/vcs-1/raspbootin_epp6hl9dpn2l5cz95jd6v3nu9/raspbootin/raspbootcom/raspbootcom''
Steps to Reproduce
clone https://github.com/chuckb/sourcedep
./gradlew run
For make to run, you will need arm cross compiler, but this is not necessary to repro this problem, as the build is not even running.
Your Environment
Mac OSX 10.14.6
Gradle wrapper 5.6.4

I did notice that in the following log, the working directory for the git clone is showing raspbootin_epp6hl9dpn2l5cz95jd6v3nu9/raspbootin yet the repo is cloned into the parent.
charles-benedicts-macbook:sourcedep chuck_benedict$ ./gradlew run --info
Initialized native services in: /Users/chuck_benedict/.gradle/native
The client will now receive all logging from the daemon (pid: 20328). The daemon log file: /Users/chuck
_benedict/.gradle/daemon/5.6.4/daemon-20328.out.log
Starting 120th build in daemon [uptime: 10 hrs 24 mins 50.314 secs, performance: 99%, non-heap usage: 34% of 268.4 MB]
Using 8 worker leases.
Starting Build
Settings evaluated using settings file '/Users/chuck_benedict/Projects/sourcedep/settings.gradle'.
Projects loaded. Root project using build file '/Users/chuck_benedict/Projects/sourcedep/build.gradle'.
Included projects: [root project 'sourcedep']

> Configure project :raspbootin
Evaluating project ':raspbootin' using build file '/Users/chuck_benedict/Projects/sourcedep/.gradle/vcs-1/raspbootin_epp6hl9dpn2l5cz95jd6v3nu9/raspbootin/build.gradle'.
Invalidating in-memory cache of /Users/chuck_benedict/Projects/sourcedep/.gradle/vcs-1/raspbootin_epp6hl9dpn2l5cz95jd6v3nu9/raspbootin/.gradle/buildOutputCleanup/outputFiles.bin

> Configure project :raspbootin:raspbootcom
Evaluating project ':raspbootin:raspbootcom' using build file '/Users/chuck_benedict/Projects/sourcedep/.gradle/vcs-1/raspbootin_epp6hl9dpn2l5cz95jd6v3nu9/raspbootin/raspbootcom/build.gradle'.

> Configure project :raspbootin:raspbootin2
Evaluating project ':raspbootin:raspbootin2' using build file '/Users/chuck_benedict/Projects/sourcedep/.gradle/vcs-1/raspbootin_epp6hl9dpn2l5cz95jd6v3nu9/raspbootin/raspbootin2/build.gradle'.

> Configure project :
Evaluating root project 'sourcedep' using build file '/Users/chuck_benedict/Projects/sourcedep/build.gradle'.
Populating VCS workingDir raspbootin_epp6hl9dpn2l5cz95jd6v3nu9/raspbootin with ref master: 8d40cf463af8f7b4bf5cb8354c4dfe51e2f50ab8
Registering project ':raspbootin' in composite build. Will substitute for module 'com.github.chuckb:raspbootin'.
Registering project ':raspbootin:raspbootcom' in composite build. Will substitute for module 'com.github.chuckb.raspbootin:raspbootcom'.
Registering project ':raspbootin:raspbootin2' in composite build. Will substitute for module 'com.github.chuckb.raspbootin:raspbootin2'.
All projects evaluated.
Selected primary task 'run' from project :
Tasks to be executed: [task ':run']
:run (Thread[Execution worker for ':',5,main]) started.

> Task :run FAILED
Caching disabled for task ':run' because:
  Build cache is disabled
Task ':run' is not up-to-date because:
  Task has not declared any outputs despite executing actions.
Starting process 'command '/Users/chuck_benedict/Projects/sourcedep/.gradle/vcs-1/raspbootin_epp6hl9dpn2l5cz95jd6v3nu9/raspbootin/raspbootcom/raspbootcom''. Working directory: /Users/chuck_benedict/Projects/sourcedep Command: /Users/chuck_benedict/Projects/sourcedep/.gradle/vcs-1/raspbootin_epp6hl9dpn2l5cz95jd6v3nu9/raspbootin/raspbootcom/raspbootcom
:run (Thread[Execution worker for ':',5,main]) completed. Took 0.005 secs.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':run'.
> A problem occurred starting process 'command '/Users/chuck_benedict/Projects/sourcedep/.gradle/vcs-1/raspbootin_epp6hl9dpn2l5cz95jd6v3nu9/raspbootin/raspbootcom/raspbootcom''

* Try:
Run with --stacktrace option to get the stack trace. Run with --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 1s
1 actionable task: 1 executed

I solved my own problem. 1) The directory that the project was downloaded into was correct and further was being resolved to the correct. 2) I was missing a dependsOn configurations.deployment clause in my run task, to cause the build to run on the source dependency.


change in Hetzner API - 1 OCT 2023

Dear @vitobotta
Please be aware of the API change.
https://status.hetzner.com/incident/21307528-ede6-4a43-8641-3fdd6fbb03fe
Please feel free to close this issue if there is no impact due to this change.

Hi, thanks for sharing. It doesn't seem to affect us from what I can see so I'll close this for now.


Add raw container (copilot) integration test

Tracking issue

https://github.com/flyteorg/flyte/issues/5930
Why are the changes needed?
To prevent in the future, someone writing code that will break the copilot.

What changes were proposed in this pull request?
Add code tests/flytekit/unit/core/test_local_raw_container.py to tests/flytekit/integration/remote/test_remote.py.

How was this patch tested?

Setup process
Screenshots
Check all the applicable boxes

[x] I updated the documentation accordingly.
[x] All new and existing tests passed.
[x] All commits are signed-off.

Related PRs
https://github.com/flyteorg/flytekit/pull/2887

Docs link

The current issue with this PR is that the integration test environment is unable to locate the Docker server needed to build the copilot image.

I tried using subprocess to build the image, but there's no docker command
line 22, in build_docker_image
    subprocess.run(
      File "/usr/local/lib/python3.9/subprocess.py", line 505, in run
    with Popen(*popenargs, **kwargs) as process:
      File "/usr/local/lib/python3.9/subprocess.py", line 951, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
      File "/usr/local/lib/python3.9/subprocess.py", line 1837, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)

Message:

    FileNotFoundError: [Errno 2] No such file or directory: 'docker'


Input field looses focus

Describe the bug
If I type in the Task Definition > Retries field the input looses focus. The same issue can be replicated across different types of FEEL (optional) fields.

Steps to reproduce

Write = some expression into a Task Definition > Retries field
Remove expression (all content)
Type = s again in the field
Input is no longer focussed

Expected behavior
Input keeps focus when field turns into an expression field
Environment

OS: Linux
Camunda Modeler Version: v5.28.0 (works in v5.27.0)
Execution Platform: Camunda 8
Installed plug-ins: None

Additional context
No response

I can reproduce it in v5.28 but cannot in v5.27.

I cannot reproduce this in the core libraries (bpmn-js-properties-panel main) either.

Let's check if we can reproduce it before the form-js update.

camunda-bpmn-js#main works fine

74bf2252e24e2883384ade79d4933a32cd218e9c is good (before form-js update)

This one is broken by 8f6662dc5a8e6e558a6d2052a747b5654673d031 too. So it's form-js update again.

Right now I am puzzled. The bug is not present in the forms though (there's flickering but it's a different topic):
https://github.com/user-attachments/assets/37df1521-1f99-4846-88d8-c4b12daf1cac

Current guess is that it's something about preact or diagram-js-ui.

So @bpmn-io/properties-panel ships with<EMAIL_ADDRESS>and there is also<EMAIL_ADDRESS>in node_modules.

Both are (should be) isolated from each other though.

Yes, and this does not change with the broken commit.

Any ideas?

Right now, the only solution I can see is to revert the update, and figure this out later.

Let's try this.

LOL. I installed the outdated forms dependencies and pinned them, but that did not fix the problem :D

"Fix" coming via https://github.com/camunda/camunda-modeler/pull/4563

Closed via https://github.com/camunda/camunda-modeler/pull/4563.


UX improvement: utilise Force Touch for equaliser controls

When moving an equaliser slider to the center, it would be useful to utilise Force Touch to notify the user with a haptic feedback when one of the sliders is back to zero.

The pages app uses Force Touch in a similar way: when aligning elements, the trackpad shows a haptic feedback when a text box is centered, for example.

Useful feature, will add in the next update

Implemented in 6f9b3421413c7c9f08dcfa20b185a39cfcaf2082

Hey everyone. Excuse me for the lack of updates. I have been really busy on the new version of eqMac. I am happy to announce an open beta release.
You can download it here: https://eqmac.app
There are a lot of known bugs that I could not fix just yet:

Driver not installing from the first try. Sometimes need to restart eqMac a couple times.
Complex Device switching logic is not perfect (for example when switching off the device that's currently playing, plugging in new device etc.)
UI takes long to load (a lot can be done to improve that)
UI dimensions are not synching properly
There's a noticeable audio delay in the playback, so not suitable for video yet (I know where the problem lies just haven't had the time to fix yet)
Sometimes the playback doesn't start, in that case please try to switch the output to the device you want and eqMac should try and build the audio pipeline again.

So as you can see there's still some work to be done but at least it's a completely modern tech stack that I am fully willing to work on: 100% Swift, User Space driver and a Web UI, instead of C++, Kernel Drivers. As I said, should work on Catalina and should not have any pesky ear drum blasting volume bugs (at least I didn't come across any).
I'm open to feedback and issue reports here: https://github.com/bitgapp/eqmac
That repo will become the main repo for eqMac and this repo will be archived eventually.
And yes it's called just eqMac, not eqMac3 :) And it will stay that way forever.

Hey everyone 👋
I will be open sourcing the new version of eqMac, therefore, I am closing this issue and repository as I will be transfering nodeful/eqMac2 repo to bitgapp/eqMac
Please bear with me for the next couple of days as I setup that new repo. The eqMac2 code will be living in the old-eqMac2 branch if anyone is interested in referencing it for whatever reason.
Please try out the new version and report bugs to the new repo.
Thanks for using eqMac.


Generalize FIP power levels

This is a long term update request from @hagikent @ZhixiaoSu

We would like the ability to programmatically set the output power levels in the three FIP channels from the GUI.
Each rig needs to have a calibration file that measures the input power to output power.
Then the GUI will use the calibration file to determine required input power level.
The GUI will pass the instructions as a string to Teensy, like C_1000_900_800 for the input power levels for the three channels

At the level of GUI, RAs will enter e.g. 470nm: 20 uW, 415nm: 15 uW, 560nm: 30 uW
Then we should keep those 20/15/30 values in the patch_cord_output_power of fiber_connectons in session.json
linking @XX-Yin for future session metadata integration

At the level of GUI, RAs will enter e.g. 470nm: 20 uW, 415nm: 15 uW, 560nm: 30 uW Then we should keep those 20/15/30 values in the patch_cord_output_power of fiber_connectons in session.json
linking @XX-Yin for future session metadata integration

I can add them to the session.json

@hagikent @ZhixiaoSu is this an issue that has been resolved? Wondering if you decided to use different modes (Axon, Normal) instead of manual settings.

@hagikent @ZhixiaoSu please see the above comment

@hagikent is this issue still applicable?


[Arc] ...Open Url in incognito

Extension
https://www.raycast.com/the-browser-company/arc
Description
hello, would it be possible to be able to define a url when opening the incognito page. Thanks
Who will benefit from this feature?
Everyone because it's cool ;)
Anything else?
No response

@pernielsentikaer i think you can close that one 😃


Add CORS header for Sentry

This may address CORS concerns for calls to sentry.tools.element.io

Merging to test on prod


Update CODEOWNERS

Removes myself from CODEOWNERS for the upcoming transition.

Closing in favor of: https://github.com/gruntwork-io/terraform-aws-utilities/pull/70


bug: request.messageBody should set with newValue

The setter for the RestRequest.messageBody field should use newValue.

Codecov Report

Merging #8 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master       #8   +/-   ##
=======================================
  Coverage   44.64%   44.64%
=======================================
  Files           7        7
  Lines         598      598
=======================================
  Hits          267      267
  Misses        331      331

Flag
Coverage Δ

#SwiftyRequest
44.64% <0%> (ø)
:arrow_up:

Impacted Files
Coverage Δ

Sources/SwiftyRequest/RestRequest.swift
56.98% <0%> (ø)
: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 2f031ac...8354a5f. Read the comment docs.

Closing this PR (fix and tests were merged several weeks ago).


islocked('b:.changedtick') fails

Using vim-8.0.342 echo islocked('b:.changedtick') results in
E46: Cannot change read-only variable "b:.changedtick"
-1

while it should yield 1 like b:changedtick.

Actually this applies to any DI_FLAGS_RO value, e.g. islocked('v:.count').

Nikolai Pavlov wrote:

Actually this applies to any DI_FLAGS_RO value, e.g. islocked('v:.count').

Works fine for me, so long as I remove the dot that should not be there.
--
EXPERIENCE - experience is a wonderful thing. It enables you to
recognise a mistake when you make it again.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

so long as I remove the dot that should not be there.

The dot is intentional.  It's the dot notation for accessing keys in a Dictionary.

@brammool This is not fine. First, this shows yet another inconsistency between different notations. Second, dictionary with variables in not guaranteed to be b: and let d = b:|call islocked('d.changedtick') errors out just in the same fashion. E.g. consider writing a serializer which saves containers with locked status and it is unable to serialize b: (such thing may be useful for debugging: :let b: is not showing locked status). Third, I am not changing a variable. If islocked() attempts or it seems like islocked() may attempt changing a variable this looks very strange and makes function very suspicious. Fourth, there is an existing key, syntactically correct and valid expression (which may even be used to obtain count) and it still errors out.
By the way, why islocked('v:count') is zero and there are no functions like isfixed()?

Nikolai Pavlov wrote:

@brammool This is not fine. First, this shows yet another
inconsistency between different notations. Second, dictionary with
variables in not guaranteed to be b: and let d = b:|call islocked('d.changedtick') errors out just in the same fashion. E.g.
consider writing a serializer which saves containers with locked
status and it is unable to serialize b: (such thing may be useful for
debugging: :let b: is not showing locked status). Third, I am not
changing a variable. If islocked() attempts or it seems like
islocked() may attempt changing a variable this looks very strange
and makes function very suspicious. Fourth, there is an existing key,
syntactically correct and valid expression (which may even be used to
obtain count) and it still errors out.

OK, islocked('d.changedtick') is something that should work.
I never intended b:.changedtick to be a valid syntax.  It's ugly.
I suppose we can't make that an error now, for backwards compability.

By the way, why islocked('v:count') is zero and there are no
functions like isfixed()?

Been like that forever.  v:count is read-only, and there is no
isreadonly().
We can probably remove the locked flag on b:changedtick, for
consistency.
The locking is something under user control, with :lockvar and
:unlockvar.  Read-only and fixed are not properties the user can change.
Thus it's not really needed to have a function to check for that.
--
It doesn't really matter what you are able to do if you don't do it.
(Bram Moolenaar)
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

2017-02-21 22:47 GMT+03:00 Bram Moolenaar<EMAIL_ADDRESS>
Nikolai Pavlov wrote:

@brammool This is not fine. First, this shows yet another
inconsistency between different notations. Second, dictionary with
variables in not guaranteed to be b: and let d = b:|call islocked('d.changedtick') errors out just in the same fashion. E.g.
consider writing a serializer which saves containers with locked
status and it is unable to serialize b: (such thing may be useful for
debugging: :let b: is not showing locked status). Third, I am not
changing a variable. If islocked() attempts or it seems like
islocked() may attempt changing a variable this looks very strange
and makes function very suspicious. Fourth, there is an existing key,
syntactically correct and valid expression (which may even be used to
obtain count) and it still errors out.

OK, islocked('d.changedtick') is something that should work.
I never intended b:.changedtick to be a valid syntax. It's ugly.
I suppose we can't make that an error now, for backwards compability.

It is a direct consequence of existence of b: scope dictionary
variable and short form of dictionary indexing syntax, making it not
work would be inconsistent and not only incompatible. I sometimes use
things like funccall(args).key.

By the way, why islocked('v:count') is zero and there are no
functions like isfixed()?

Been like that forever. v:count is read-only, and there is no
isreadonly().
We can probably remove the locked flag on b:changedtick, for
consistency.

I intentionally added it there because islocked('b:changedtick')
intentionally returned 1, I did not try to understand why it does so.
I do not know whether somebody actually depends on that, but think it
is unlikely because b:changedtick was not previously in a b:
dictionary so whatever you did you needed to handle this value
separately; actually it is more likely that something will break
because of b:changedtick suddenly appearing inside a b: dictionary
then because of islocked('b:changedtick') starting to return 0 in
place of 1.

The locking is something under user control, with :lockvar and
:unlockvar. Read-only and fixed are not properties the user can change.
Thus it's not really needed to have a function to check for that.

I do not have a use-case except that it is slightly easier to check
isfixed/isreadonly in Vim own tests then checking that
assigning/unletting fails. Does not matter much because checking for
failures is more robust then checking for function output.
It would be needed if you plan on adding more such special variables
to scope dictionaries in the future, to make scripts forwards
compatible (e.g. if you need to save and restore b: dictionary
contents it would be good idea to honor isreadonly() to not get
error messages, now you may just special-case b:changedtick), but this
idea is not backwards compatible: consider a script which used
variable b:number and you added readonly b:number with bufnr() of
this buffer. Previously legal script suddenly broken. (I also think
this is what justifies user functions and commands forcing to begin
with upper case letter.)

--
It doesn't really matter what you are able to do if you don't do it.
(Bram Moolenaar)
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net \
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\ an exciting new programming language -- http://www.Zimbu.org ///
\\ help me help AIDS victims -- http://ICCF-Holland.org ///
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to<EMAIL_ADDRESS>For more options, visit https://groups.google.com/d/optout.

fixed as of 3a257737726ba42 (8.0.0345)

Nikolai Pavlov wrote:

@brammool This is not fine. First, this shows yet another
inconsistency between different notations. Second, dictionary with
variables in not guaranteed to be b: and let d = b:|call islocked('d.changedtick') errors out just in the same fashion. E.g.
consider writing a serializer which saves containers with locked
status and it is unable to serialize b: (such thing may be useful for
debugging: :let b: is not showing locked status). Third, I am not
changing a variable. If islocked() attempts or it seems like
islocked() may attempt changing a variable this looks very strange
and makes function very suspicious. Fourth, there is an existing key,
syntactically correct and valid expression (which may even be used to
obtain count) and it still errors out.

OK, islocked('d.changedtick') is something that should work.
I never intended b:.changedtick to be a valid syntax. It's ugly.
I suppose we can't make that an error now, for backwards compability.

It is a direct consequence of existence of b: scope dictionary
variable and short form of dictionary indexing syntax, making it not
work would be inconsistent and not only incompatible. I sometimes use
things like funccall(args).key.

I was talking about the syntax, not the semantics.  Although b: behaves
like a dictionary, it's a namespace in which members are accessed
directly, without a separating ".".

By the way, why islocked('v:count') is zero and there are no
functions like isfixed()?

Been like that forever. v:count is read-only, and there is no
isreadonly().
We can probably remove the locked flag on b:changedtick, for
consistency.

I intentionally added it there because islocked('b:changedtick')
intentionally returned 1, I did not try to understand why it does so.
I do not know whether somebody actually depends on that, but think it
is unlikely because b:changedtick was not previously in a b:
dictionary so whatever you did you needed to handle this value
separately; actually it is more likely that something will break
because of b:changedtick suddenly appearing inside a b: dictionary
then because of islocked('b:changedtick') starting to return 0 in
place of 1.

Other read-only variables are also not considered locked.  Let's keep it
consistent.

The locking is something under user control, with :lockvar and
:unlockvar. Read-only and fixed are not properties the user can change.
Thus it's not really needed to have a function to check for that.

I do not have a use-case except that it is slightly easier to check
isfixed/isreadonly in Vim own tests then checking that
assigning/unletting fails. Does not matter much because checking for
failures is more robust then checking for function output.
It would be needed if you plan on adding more such special variables
to scope dictionaries in the future, to make scripts forwards
compatible (e.g. if you need to save and restore b: dictionary
contents it would be good idea to honor isreadonly() to not get
error messages, now you may just special-case b:changedtick), but this
idea is not backwards compatible: consider a script which used
variable b:number and you added readonly b:number with bufnr() of
this buffer. Previously legal script suddenly broken. (I also think
this is what justifies user functions and commands forcing to begin
with upper case letter.)

Making variables writeable just to be able to save/restore them is
tricky.  It opens the possibility to write any time and cause harm.
If needed, we could add specific save and restore functions.  But that's
just in general, there can be exceptions for historic reasons...
b:changedtick should never be saved/restored anyway, it only ever
increments.  That is its purpose.
--
login: yes
password: I don't know, please tell me
password is incorrect
login: yes
password: incorrect
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

2017-02-23 16:25 GMT+03:00 Bram Moolenaar<EMAIL_ADDRESS>

Nikolai Pavlov wrote:

@brammool This is not fine. First, this shows yet another
inconsistency between different notations. Second, dictionary with
variables in not guaranteed to be b: and let d = b:|call islocked('d.changedtick') errors out just in the same fashion. E.g.
consider writing a serializer which saves containers with locked
status and it is unable to serialize b: (such thing may be useful for
debugging: :let b: is not showing locked status). Third, I am not
changing a variable. If islocked() attempts or it seems like
islocked() may attempt changing a variable this looks very strange
and makes function very suspicious. Fourth, there is an existing key,
syntactically correct and valid expression (which may even be used to
obtain count) and it still errors out.

OK, islocked('d.changedtick') is something that should work.
I never intended b:.changedtick to be a valid syntax. It's ugly.
I suppose we can't make that an error now, for backwards compability.

It is a direct consequence of existence of b: scope dictionary
variable and short form of dictionary indexing syntax, making it not
work would be inconsistent and not only incompatible. I sometimes use
things like funccall(args).key.

I was talking about the syntax, not the semantics.  Although b: behaves
like a dictionary, it's a namespace in which members are accessed
directly, without a separating ".".

By the way, why islocked('v:count') is zero and there are no
functions like isfixed()?

Been like that forever. v:count is read-only, and there is no
isreadonly().
We can probably remove the locked flag on b:changedtick, for
consistency.

I intentionally added it there because islocked('b:changedtick')
intentionally returned 1, I did not try to understand why it does so.
I do not know whether somebody actually depends on that, but think it
is unlikely because b:changedtick was not previously in a b:
dictionary so whatever you did you needed to handle this value
separately; actually it is more likely that something will break
because of b:changedtick suddenly appearing inside a b: dictionary
then because of islocked('b:changedtick') starting to return 0 in
place of 1.

Other read-only variables are also not considered locked.  Let's keep it
consistent.

The locking is something under user control, with :lockvar and
:unlockvar. Read-only and fixed are not properties the user can change.
Thus it's not really needed to have a function to check for that.

I do not have a use-case except that it is slightly easier to check
isfixed/isreadonly in Vim own tests then checking that
assigning/unletting fails. Does not matter much because checking for
failures is more robust then checking for function output.
It would be needed if you plan on adding more such special variables
to scope dictionaries in the future, to make scripts forwards
compatible (e.g. if you need to save and restore b: dictionary
contents it would be good idea to honor isreadonly() to not get
error messages, now you may just special-case b:changedtick), but this
idea is not backwards compatible: consider a script which used
variable b:number and you added readonly b:number with bufnr() of
this buffer. Previously legal script suddenly broken. (I also think
this is what justifies user functions and commands forcing to begin
with upper case letter.)

Making variables writeable just to be able to save/restore them is
tricky.  It opens the possibility to write any time and cause harm.
If needed, we could add specific save and restore functions.  But that's
just in general, there can be exceptions for historic reasons...
b:changedtick should never be saved/restored anyway, it only ever
increments.  That is its purpose.

I did not mean to make anything writeable. I meant that assuming you
have code which saves and restores b: variables you need to handle
cases like “variable can be saved, but can’t be restored”. There
currently is a single case with b:changedtick (or saving/restoring a
very few writeable values in v:, but I have not seen a use-cases so
far), but if there are plans on making more something like
isreadonly() would be good to have: I would normally use deepcopy()
and filter(, 'isreadonly('b:'.v:key)) then than iterating over
keys(b:) (in which case it would be easy to check whether let b:{key} = b:{key} fails): this is not only less code to write, it
also aligns will with main VimL optimization principle: the less Ex
commands the faster the code.
If b:changedtick keeps staying unique it is enough to just
special-case only it for this purpose. If there will be more in the
future then isreadonly() is needed to nicely keep forward
compatibility.

--
login: yes
password: I don't know, please tell me
password is incorrect
login: yes
password: incorrect
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


Includes react-native-material-kit

Hi, thanks for the great work!
Would you consider including react-native-material-kit in the app? It's amazing to put a live demo and playground on the module's home page.

Sure thing! One question, I noticed you mentioned you're porting it to javascript. Is that ready yet or do you want to have the native version included?

Thanks @jsierles,
There's still some legacy code written in objc, so it's still a native module.

Included in the latest release.

Thanks, it's awesome!


unzip missing

Traceback (most recent call last):   File "/workspace/dhl/VBench/run_eval.py", line 166, in      main()   File "/workspace/dhl/VBench/run_eval.py", line 152, in main     my_VBench.evaluate(   File "/workspace/dhl/VBench/vbench/init.py", line 144, in evaluate     submodules_dict = init_submodules(dimension_list, local=local, read_frame=read_fram e)   File "/workspace/dhl/VBench/vbench/utils.py", line 279, in init_submodules     subprocess.run(unzip_command, check=True)   File "/workspace/rlsu/miniconda3/envs/vbench/lib/python3.10/subprocess.py", line 503,  in run     with Popen(*popenargs, **kwargs) as process:   File "/workspace/rlsu/miniconda3/envs/vbench/lib/python3.10/subprocess.py", line 971,  in init     self._execute_child(args, executable, preexec_fn, close_fds,   File "/workspace/rlsu/miniconda3/envs/vbench/lib/python3.10/subprocess.py", line 1863 , in _execute_child     raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'unzip'
need to update requirenment.txt

https://github.com/Vchitect/VBench/pull/49

Another issue when testing dimension "color"
Traceback (most recent call last):
  File "/workspace/dhl/VBench/run_eval.py", line 166, in <module>
    main()
  File "/workspace/dhl/VBench/run_eval.py", line 152, in main
    my_VBench.evaluate(
  File "/workspace/dhl/VBench/vbench/__init__.py", line 157, in evaluate
    results = evaluate_func(cur_full_info_path, self.device, submodules_list, **kwargs)
  File "/workspace/dhl/VBench/vbench/object_class.py", line 54, in compute_object_class
    dense_caption_model.initialize_model_det(**submodules_dict)
  File "/workspace/dhl/VBench/vbench/third_party/grit_model.py", line 17, in initialize_model_det
    self.demo = init_demo(self.device, model_weight = model_weight, task="ObjectDet")
  File "/workspace/dhl/VBench/vbench/third_party/grit_src/image_dense_captions.py", line 109, in init_demo
    demo = VisualizationDemo(cfg)
  File "/workspace/dhl/VBench/vbench/third_party/grit_src/grit/predictor.py", line 102, in __init__
    self.predictor = SingleDefaultPredictor(cfg)
  File "/workspace/rlsu/miniconda3/envs/vbench/lib/python3.10/site-packages/detectron2/engine/defaults.py", line 288, in __init__
    checkpointer.load(cfg.MODEL.WEIGHTS)
  File "/workspace/rlsu/miniconda3/envs/vbench/lib/python3.10/site-packages/detectron2/checkpoint/detection_checkpoint.py", line 62, in load
    ret = super().load(path, *args, **kwargs)
  File "/workspace/rlsu/miniconda3/envs/vbench/lib/python3.10/site-packages/fvcore/common/checkpoint.py", line 155, in load
    checkpoint = self._load_file(path)
  File "/workspace/rlsu/miniconda3/envs/vbench/lib/python3.10/site-packages/detectron2/checkpoint/detection_checkpoint.py", line 99, in _load_file
    loaded = self._torch_load(filename)
  File "/workspace/rlsu/miniconda3/envs/vbench/lib/python3.10/site-packages/detectron2/checkpoint/detection_checkpoint.py", line 114, in _torch_load
    return super()._load_file(f)
  File "/workspace/rlsu/miniconda3/envs/vbench/lib/python3.10/site-packages/fvcore/common/checkpoint.py", line 252, in _load_file
    return torch.load(f, map_location=torch.device("cpu"))
  File "/workspace/rlsu/miniconda3/envs/vbench/lib/python3.10/site-packages/torch/serialization.py", line 1004, in load
    with _open_zipfile_reader(opened_file) as opened_zipfile:
  File "/workspace/rlsu/miniconda3/envs/vbench/lib/python3.10/site-packages/torch/serialization.py", line 456, in __init__
    super().__init__(torch._C.PyTorchFileReader(name_or_buffer))
RuntimeError: PytorchStreamReader failed reading zip archive: failed finding central directory
/workspace/rlsu/miniconda3/envs/vbench/lib/python3.10/site-packages/huggingface_hub/file_download.py:1132: FutureWarning: `resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.
  warnings.warn(

@ziqihuangg  @NattapolChan

unzip should be command-line tool not the one from Pypi package.
sudo apt-get install unzip

Hi, we're closing the issue since there is no follow-up question, but feel free to re-open it if you have any further questions!


Change default video settings on launch?

Hi, really new to MPV in general. Wanted to know if there's a way to change the launch settings - for instance, I would like to use the video's native resolution and have it sound muted on launch. Would that be through the 360plugin.lua file? Would the process be any different from the standard MPV player?

As best I can tell, the answer is "sorta."  Basically, you need to set options for this specific script separately from options for mpv.  Anything that's in the opts table in the script needs to be changed via --script-opts, while something like volume would need to be passed in a separate option to mpv directly.
So for example:
mpv --volume=-1 --script=360plugin.lua --script-opts=360plugin-enabled [filename]

For the resolution part, this requires editing the script itself.  There's a variable res defined at the beginning, and it defines the resolution at which the file runs.  As best I can tell it's a scaling factor of some kind: a value of 1 resulted in a resolution that is 1/10 native on the one file I've tried, while a value of 10 was native.  I haven't tried it, but I'm assuming that anything above 10 means mpv will try to upscale it.
The simplest way to address this, then, is simply to edit the res variable (line 91) to be 10.
I got a tad fancier: I added an option for it to the opts table, then combined that with a bash script that allows an optional value to be passed.  But this is a little bit extra :)

Thanks that worked! I'll stick to simple changes for the time being ha!


After Update 2023.11.0

After the last update (2023.11.0) Scripts and Automations has no Function. Backup to 2023.10.5 bring Funktion back.
Where is the Problem?

Hello,
What do you mean by "no Function" ? Have they stopped working ? Which sensors are you using as triggers ?
PS: I always answer in the language of the question but we can do this in french ;)

Hello and thank you for the quick response!
French unfortunately not better than English, I am German 🤷♂
I use an automation and a script that switches the respective tariffs blue, white, red etc..
I think it's the device ID. This will probably be changed by the update. This behaviour has also been noted in the release discussions.
See https://community.home-assistant.io/t/2023-11-to-do-add-release-title/634647/33
Cdt RolfAm 02.11.2023 um 12:38 schrieb Edouard Hur @.***>:
Hello,
What do you mean by "no Function" ? Have they stopped working ? Which sensors are you using as triggers ?
PS: I always answer in the language of the question but we can do this in french ;)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

What is bothering me is that I do not have a single error log that would point to a specific problem and so a specific solution.
IDs have not been change by the extension so if HA has changed the way is generate its IDs, I am afraid that I can not do much to get the old ones back.
I need to dig this issue to better understand what is going on.

I did the upgrade to 2023.11 but it seems that my entities did not changed IDs (or I would not have history for them) :

And my automatisations seems fine too :

I am gonna need more information / logs / screenshots in order to help you, from what I see on my side everything seems fine (yet).

For the RTE integration, the client ID and the secret are returned via the API.
The ID was then also used in the automations and in the script. See attachment.
After the update, I can neither call up, view or edit the automations nor the script.Am 02.11.2023 um 14:40 schrieb Edouard Hur @.***>:
I did the upgrade to 2023.11 but it seems that my entities did not changed IDs (or I would not have history for them) :
And my automatisations seems fine too :
I am gonna need more information / logs / screenshots in order to help you, from what I see on my side everything seems fine (yet).
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Unfortunately the attachment did not make it thru github with reply by email function. Please upload it directly within the github interface.

👍 did it

Am 02.11.2023 um 15:17 schrieb Rolf Hoefel @.***>:
For the RTE integration, the client ID and the secret are returned via the API.
The ID was then also used in the automations and in the script. See attachment.
After the update, I can neither call up, view or edit the automations nor the script.

any Idea?

This is weird :

The ID you have in your first screenshot is the application ID you created from RTE tu use the API
The device_id of the Home Assistant device is something entirely different, internal of HA

Both you not match in any way.
For example, if I setup an automation with the same trigger as yours:

This translates to the following YAML:

Which no way near my RTE API Application ID:

So I am not sure how you ended up in this situation but I would recommend to edit your automation and recreate the trigger with the UI to get the correct HA device_id.

ok, I'll adjust my automation and the script.
I'll know more the next time I switch between HP and HC.
Many thanksCdt RolfAm 04.11.2023 um 09:38 schrieb Edouard Hur @.***>:
This is weird :
The ID you have in your first screenshot is the application ID you created from RTE tu use the API
The device_id of the Home Assistant device is something entirely different, internal of HA
Both you not match in any way.
For example, if I setup an automation with the same trigger as yours:
This translates to the following YAML:
Which no way near my RTE API Application ID:
So I am not sure how you ended up in this situation but I would recommend to edit your automation and recreate the trigger with the UI to get the correct HA device_id.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Good morning,
Everything works, even after the 2023.11.x update.
Without your help I would certainly not have solved the problem so quickly. Many thanks for that.
Greetings
Rolf alias Binifada

Thanks for letting me know that everything is in order 👍


Auto expiring devices don't get cleaned up in DNS Host Privacy list

It seems that if an expiring devices is added to any of the DNS log settings they actually don't get removed when the device expired. The device disappeared but its IP still is in the Host Privacy IP list.
Cheers

coredns-jsonlog has a branch to test now for handling the delete event from api, new in v0.3.14

v0.3.14 is now released


[WIP] Add troubleshooting sections

@mgiammar @pjgrandinetti PR #92 is going to create a notebook merge conflict nightmare with other doc PRs. I suggest copy only the relevant .rst file from here and create a new PR. Let's close this one.

@deepanshs @pjgrandinetti I agree. The troubleshooting sections can be added in other PRs

Has been addressed in #98


Allow port 80 for certificate renewal

Let's Encrypt requires port 80 to be open for certificate renewal. This commit adds port 80 to the firewall rules for coturn when using TLS.

OH! Sorry somehow I missed this PR completely.
Will work on it right away.

Moved to PR #10


Authentication/Security

We need to have some sort of support for the Authentication/Security being defined in the RFB specification.
makes sense to support V3.3, V3.7 and V3.8 then as the RFB protocol differs for this functionality.

The simple VNC Authentication is implemented now.


Fix build errors on Unix

This gets the launcher building and running on Linux (and Mac, though I haven't tested it). There are still some more things to fix, not including implementing the actual proxying which I won't implement in this PR.

@RBNXI I'm guessing you're missing the Tauri development prerequisites: https://tauri.app/v1/guides/getting-started/prerequisites

@RBNXI Try installing yarn and running yarn start:dev. You can also just run the command manually, which can be found in package.json

@RBNXI Ty for letting me know I'll just pop that in rq instead

I might not have time to fix everything I intended, so I think we should merge this for now. Also we'll probably have to change a lot of the path handling code on the backend first, as right now it mostly works with String/str instead of PathBuf/Path, and that will break things.

Fair enough, appreciate the work, I will make a point of converting what I can to PathBuf at some point


HADOOP-18547. Check if config value is not empty string in AbfsConfiguration.getMandatoryPasswordString()

JIRA: https://issues.apache.org/jira/browse/HADOOP-18547
Also fixing below test-failure as part of pr:
[ERROR] TestAccountConfiguration.testConfigPropNotFound:386->testMissingConfigKey:399 Expected a org.apache.hadoop.fs.azurebfs.contracts.exceptions.TokenAccessProviderException to be thrown, but got the result: : "org.apache.hadoop.fs.azurebfs.oauth2.ClientCredsTokenProvider"
Testing
:::: AGGREGATED TEST RESULT ::::
HNS-OAuth
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR]   TestExponentialRetryPolicy.testOperationOnAccountIdle:216 » AccessDenied Opera...
[INFO]
[ERROR] Tests run: 112, Failures: 0, Errors: 1, Skipped: 1
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR]   ITestAzureBlobFileSystemLease.testAcquireRetry:329 » TestTimedOut test timed o...
[ERROR]   ITestAzureBlobFileSystemOauth.testBlobDataContributor:84 » AccessDenied Operat...
[ERROR]   ITestAzureBlobFileSystemOauth.testBlobDataReader:143 » AccessDenied Operation ...
[INFO]
[ERROR] Tests run: 568, Failures: 0, Errors: 3, Skipped: 99
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR]   ITestAbfsTerasort.test_120_terasort:262->executeStage:206 » IO The ownership o...
[INFO]
[ERROR] Tests run: 336, Failures: 0, Errors: 1, Skipped: 55
HNS-SharedKey
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR]   TestExponentialRetryPolicy.testOperationOnAccountIdle:216 » AccessDenied Opera...
[INFO]
[ERROR] Tests run: 112, Failures: 0, Errors: 1, Skipped: 2
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR]   ITestAzureBlobFileSystemLease.testAcquireRetry:329 » TestTimedOut test timed o...
[INFO]
[ERROR] Tests run: 568, Failures: 0, Errors: 1, Skipped: 54
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR]   ITestAbfsFileSystemContractDistCp>AbstractContractDistCpTest.testDistCpUpdateCheckFileSkip:919->AbstractContractDistCpTest.verifySkipAndCopyCounter:1000->Assert.assertEquals:647->Assert.failNotEquals:835->Assert.fail:89 Mismatch in COPY counter value expected:<1> but was:<0>
[INFO]
[ERROR] Tests run: 336, Failures: 1, Errors: 0, Skipped: 41
NonHNS-SharedKey
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR]   TestExponentialRetryPolicy.testOperationOnAccountIdle:216 » AccessDenied Opera...
[INFO]
[ERROR] Tests run: 112, Failures: 0, Errors: 1, Skipped: 2
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR]   ITestAzureBlobFileSystemLease.testAcquireRetry:336 » TestTimedOut test timed o...
[INFO]
[ERROR] Tests run: 568, Failures: 0, Errors: 1, Skipped: 277
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR]   ITestAbfsTerasort.test_110_teragen:244->executeStage:211->Assert.assertEquals:647->Assert.failNotEquals:835->Assert.fail:89 teragen(1000<EMAIL_ADDRESS>failed expected:<0> but was:<1>
[ERROR]   ITestAbfsFileSystemContractDistCp>AbstractContractDistCpTest.testDistCpUpdateCheckFileSkip:919->AbstractContractDistCpTest.verifySkipAndCopyCounter:1000->Assert.assertEquals:647->Assert.failNotEquals:835->Assert.fail:89 Mismatch in COPY counter value expected:<1> but was:<0>
[ERROR] Errors:
[ERROR]   ITestAbfsJobThroughManifestCommitter.test_0420_validateJob » OutputValidation ...
[ERROR]   ITestAbfsManifestCommitProtocol.testCommitLifecycle » OutputValidation abfs:/... [ERROR]   ITestAbfsManifestCommitProtocol.testCommitterWithDuplicatedCommit » OutputValidation [ERROR]   ITestAbfsManifestCommitProtocol.testConcurrentCommitTaskWithSubDir » OutputValidation [ERROR]   ITestAbfsManifestCommitProtocol.testMapFileOutputCommitter » OutputValidation ... [ERROR]   ITestAbfsManifestCommitProtocol.testOutputFormatIntegration » OutputValidation [ERROR]   ITestAbfsManifestCommitProtocol.testParallelJobsToAdjacentPaths » OutputValidation [ERROR]   ITestAbfsManifestCommitProtocol.testTwoTaskAttemptsCommit » OutputValidation ...
[INFO]
[ERROR] Tests run: 336, Failures: 2, Errors: 8, Skipped: 46
AppendBlob-HNS-OAuth
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR]   TestExponentialRetryPolicy.testOperationOnAccountIdle:216 » AccessDenied Opera...
[INFO]
[ERROR] Tests run: 112, Failures: 0, Errors: 1, Skipped: 1
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR]   ITestAzureBlobFileSystemLease.testAcquireRetry:329 » TestTimedOut test timed o...
[ERROR]   ITestAzureBlobFileSystemOauth.testBlobDataContributor:84 » AccessDenied Operat...
[ERROR]   ITestAzureBlobFileSystemOauth.testBlobDataReader:143 » AccessDenied Operation ...
[INFO]
[ERROR] Tests run: 568, Failures: 0, Errors: 3, Skipped: 99
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR]   ITestAbfsFileSystemContractAppend>AbstractContractAppendTest.testAppendNonexistentFile:85->Assert.fail:89 expected a failure
[ERROR] Errors:
[ERROR]   ITestAbfsTerasort.test_120_terasort:262->executeStage:206 » IO The ownership o...
[ERROR]   ITestAbfsFileSystemContractAppend>AbstractContractAppendTest.testAppendToExistingFile:96 » FileAlreadyExists
[INFO]
[ERROR] Tests run: 336, Failures: 1, Errors: 2, Skipped: 55

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 43s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
40m 25s

trunk passed

+1 :green_heart:
compile
0m 51s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
0m 48s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
checkstyle
0m 43s

trunk passed

+1 :green_heart:
mvnsite
0m 52s

trunk passed

-1 :x:
javadoc
0m 47s
/branch-javadoc-hadoop-tools_hadoop-azure-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-azure in trunk failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
0m 37s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
1m 23s

trunk passed

+1 :green_heart:
shadedclient
22m 49s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 36s

the patch passed

+1 :green_heart:
compile
0m 36s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
0m 36s

the patch passed

+1 :green_heart:
compile
0m 33s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
javac
0m 33s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 24s

the patch passed

+1 :green_heart:
mvnsite
0m 39s

the patch passed

-1 :x:
javadoc
0m 31s
/patch-javadoc-hadoop-tools_hadoop-azure-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-azure in the patch failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
0m 28s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
1m 13s

the patch passed

+1 :green_heart:
shadedclient
22m 27s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m  6s

hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 42s

The patch does not generate ASF License warnings.

101m 41s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5177/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5177

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 16795c941670 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / b7b2633437f60d9edbb754afb85ce7ce29b57740

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5177/1/testReport/

Max. process+thread count
728 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5177/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 37s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
38m 57s

trunk passed

+1 :green_heart:
compile
0m 59s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
0m 55s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
checkstyle
0m 52s

trunk passed

+1 :green_heart:
mvnsite
1m  1s

trunk passed

-1 :x:
javadoc
0m 59s
/branch-javadoc-hadoop-tools_hadoop-azure-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-azure in trunk failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
0m 50s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
1m 34s

trunk passed

+1 :green_heart:
shadedclient
22m 39s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 39s

the patch passed

+1 :green_heart:
compile
0m 42s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
0m 42s

the patch passed

+1 :green_heart:
compile
0m 36s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
javac
0m 36s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 26s

the patch passed

+1 :green_heart:
mvnsite
0m 41s

the patch passed

-1 :x:
javadoc
0m 31s
/patch-javadoc-hadoop-tools_hadoop-azure-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-azure in the patch failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
0m 31s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
1m 15s

the patch passed

+1 :green_heart:
shadedclient
21m 41s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 13s

hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 50s

The patch does not generate ASF License warnings.

100m 45s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5177/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5177

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 1969123ed4bd 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 2959a9cc354c625599532f47a611aca4df90b000

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5177/2/testReport/

Max. process+thread count
671 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5177/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

LGTM, if its ready for review

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  7s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
47m  8s

trunk passed

+1 :green_heart:
compile
0m 39s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
0m 35s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
checkstyle
0m 30s

trunk passed

+1 :green_heart:
mvnsite
0m 40s

trunk passed

-1 :x:
javadoc
0m 37s
/branch-javadoc-hadoop-tools_hadoop-azure-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-azure in trunk failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
0m 29s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
1m 14s

trunk passed

+1 :green_heart:
shadedclient
26m 40s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 37s

the patch passed

+1 :green_heart:
compile
0m 32s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
0m 32s

the patch passed

+1 :green_heart:
compile
0m 28s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
javac
0m 28s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 17s

the patch passed

+1 :green_heart:
mvnsite
0m 31s

the patch passed

-1 :x:
javadoc
0m 23s
/patch-javadoc-hadoop-tools_hadoop-azure-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-azure in the patch failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
0m 22s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
1m  4s

the patch passed

+1 :green_heart:
shadedclient
27m  9s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m  4s

hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 33s

The patch does not generate ASF License warnings.

114m 48s

Subsystem
Report/Notes

Docker
ClientAPI=1.42 ServerAPI=1.42 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5177/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5177

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 12a4ab51a07b 4.15.0-197-generic #208-Ubuntu SMP Tue Nov 1 17:23:37 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 1ae02b4786cc3297d2d799ccaa678707a6fb898c

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5177/3/testReport/

Max. process+thread count
613 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5177/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

LGTM, if its ready for review

@steveloughran , requesting you for your kind review. Thanks.


If /dev/log/all does not exist on the device the app fails and keeps printing "Restarting..."

My device is running Android 4.0.3 and it doesn't contain the /dev/log/all file, so I get the following error if I run 'rogcat.exe' over and over
Restarting "C:\Users\abid.esmail\AppData\Local\Android\sdk\platform-tools\adb.exe logcat -b all"
()  -    Unable to open log device '/dev/log/all': No such file or directory
Restarting "C:\Users\abid.esmail\AppData\Local\Android\sdk\platform-tools\adb.exe logcat -b all"
()  -    Unable to open log device '/dev/log/all': No such file or directory
shell@android:/dev/log $ ll
crw-rw--w- root     log       10,  55 2014-01-31 17:00 events
crw-rw--w- root     log       10,  56 2014-01-31 17:00 main
crw-rw--w- root     log       10,  54 2014-01-31 17:00 radio
crw-rw--w- root     log       10,  53 2014-01-31 17:00 system
Thanks,
Abid

Starting rogcat without any argument defaults to adb logcat -b all which works fine standard Android systems.
Your platform seems to not provide the all buffer. Doesn't mater: just provide the command yourself:
rogcat "adb logcat"


Ignore /docs in cicd workflow

Hi Freddy and Team,
as I'm using GitHub Pages for documentation purpose, it would be great if the complete /docs path could be ignored in cicd.
Even if the docs folder (and subfolders) mainly contains .md files (which are already ignored), there may be also other filetypes which now may trigger an unnecessary start of cicd workflow.
/docs is btw a standard GitHub folder to built GitHub pages from selected branch.
Thanks.

Sounds like a good idea.
Will probably make paths-ignore configurable and add /docs to the default.

Will there be future AL-GO support for auto-publishing source code documentation using aldoc.exe as part of the release action? (Incl. publishing documentation from the private source repo to a public github (pages) repo)
References

https://github.com/orgs/microsoft/projects/521/views/1?filterQuery=doc&pane=issue&itemId=27095580
https://svirlan.com/business-central-aldoc-docfx-generate-github-page-to-host-your-al-documentation/

Yes, working on that - https://github.com/microsoft/AL-Go/pull/760
Example: https://microsoft.github.io/bcsamples-bingmaps.pte/index.html

Moved to backlog


Corrected link to the spreadsheet with countries and regions

Looks like the link is no longer correct (file moved), I corrected it.

@robdy Thank you for fixing this!


automation solution for photowall

Currently the photowall is using manually entered series numbers to return digitised records from photographic series only. I offer the following solution to automate this after extensive testing:
create a query to return only digitised records from only photographic series for a given search term ;
1 Using the API query form I used text search term
2. I faceted by photograph or image.
3. I ticked the iiif manifest checkbox.
4. 3,638 results come from photographic series only. Same for  or any other term. I have done extensive testing and only photographic series records are ever returned. Please see if you can apply this automation solution to the PhotoWall tool to replace the existinmg manual approach. If it is at all possible to do this in time for our meeting next Wed 11/5 I would be verty grateful.

I will change the Photo Wall's form so that it doesn't refer to series at all, but instead restricts records to those whose record_form equals Photograph or Image and which also have some value for iiif-manifest. NB this is going to exclude the "Moving Image" records from series 12800.

fixed in 12a36a791843a5eb36589abd6d928031773ea0df

This all sounds great. There are no moving images in 12800. So should be good

Just tested ans works perfectly! enjoy your break :)


ETag does not match current item's value

I try to upload a large file. But i get an error - 412 after uploading.
Error message is "ETag does not match current item's value"
Could please someone help me with this issue?!
First, i create an upload session using - /me/drive/items/{path}:/{to}:/createUploadSession
And post it to https://graph.microsoft.com/v1.0.
After a success request i receive an upload url as a response.
Second, using an upload url i try to put a file to a OneDrive storage.
Place "Content-Length", "Content-Range" with values to a request's header and send it with a file data to upload url. After a success request i receive an drive item info with details.
Problem begins here.
First of all i can not get files from a storage.
Second, i saw in an original documentation that i need to commit an upload session. So i tried to do this. I took a received eTag an put it in "If-Match" field in headers. Also i use upload url to send it in<EMAIL_ADDRESS>param. And when i put it to OneDrive server i receive an error 412 with a message "ETag does not match current item's value". I can't understand what is wrong.
When i look into OneDrive storage, file is present and it seems everything is correct.

Thanks for your feedback.  Could you please clarify a few things?

Which doc page you were using to help guide you through the scenario?
For example, was it this one - "Resumable file upload"
https://docs.microsoft.com/en-us/graph/api/driveitem-createuploadsession?view=graph-rest-1.0
or another document, blog post, or something else?
On which request(s) did you provide the If-Match header?
For the requests that failed could you please provide more information about the requests, including headers, sample URL's, etc.:

If you have not provided the following information, could you please provide the following?
Could you please provide the following response headers:

Date (in UTC, please)
request-id
SPRequestGuid (for requests made to OneDrive for Business)

Please provide as recent values as possible.
Could you please provide sample requests and responses that illustrate the issue that you are encountering?

Thank you for a response, Chris!

Yes, it was "Resumable file upload" page.

A request - "https://graph.microsoft.com/v1.0/me/drive/root:/test/test_file.zip"

But actually it seems i was not clear regarding committing an upload session. Probably i should not make this kind of request because my previous request was success.
My real problem is that i can not get a list of files after uploading.

Correct, if the entire content of the file has been uploaded, the commit is implicit.
Also, the driveItem for the newly-completed file should be returned by the API.
Would that meet the needs of your scenario?

Sorry for a delay, but my problem is still not fixed. That is true, after an uploading of the last portion of a file i receive driveItem.
But after that i can not make any request to a OneDrive storage, a request is stuck.
In another part of my code i need to verify if a file was uploaded to a storage. I use this kind of a request - GET /me/drive/root:/{file_name} . And nothing happens.  Would you please explain me what happens after an uploading of the last portion of a file?

Could you please explain what requests do not work?

But after that i can not make any request to a OneDrive storage, a request is stuck.

When the last byte range of a file is received, assuming no conflicts such as a file name conflict, the server should respond with the driveItem object corresponding to the file that has completed uploading.

It seems, the issue fixed


improvement/OSIS-51-remove-vmware-reference-from-scality-package

Hello anurag4dsb,
My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.
Status report is not available.

Incorrect fix version
The Fix Version/s in issue OSIS-51 contains:

None

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

1.0.0

Please check the Fix Version/s of OSIS-51, or the target
branch of this pull request.

Codecov Report

Merging #82 (a52b0b1) into development/1.0 (36de5c7) will decrease coverage by 12.50%.
The diff coverage is 0.00%.

@@                  Coverage Diff                   @@
##             development/1.0      #82       +/-   ##
======================================================
- Coverage              84.84%   72.34%   -12.51%
- Complexity               267      389      +122
======================================================
  Files                     19       43       +24
  Lines                   1287     1833      +546
  Branches                 107      139       +32
======================================================
+ Hits                    1092     1326      +234
- Misses                   135      445      +310
- Partials                  60       62        +2

Impacted Files
Coverage Δ

.../main/java/com/scality/osis/model/Information.java
51.57% <ø> (ø)

...va/com/scality/osis/model/InformationServices.java
63.63% <ø> (ø)

...va/com/scality/osis/model/OsisBucketLoggingId.java
0.00% <ø> (ø)

...in/java/com/scality/osis/model/OsisBucketMeta.java
0.00% <ø> (ø)

...src/main/java/com/scality/osis/model/OsisCaps.java
66.66% <ø> (ø)

...ain/java/com/scality/osis/model/OsisConstants.java
100.00% <ø> (ø)

...rc/main/java/com/scality/osis/model/OsisError.java
0.00% <ø> (ø)

...ava/com/scality/osis/model/OsisS3Capabilities.java
10.81% <ø> (ø)

.../java/com/scality/osis/model/OsisS3Credential.java
66.66% <ø> (ø)

...c/main/java/com/scality/osis/model/OsisTenant.java
47.50% <ø> (ø)

... and 44 more

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 36de5c7...a52b0b1. Read the comment docs.


Fix/skip pre nakamoto reward set lookup

:tada: This PR is included in version 0.4.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


hyprlandPlugins.hyprgrass: init at 0.7.0, wf-touch: init at 0-unstable-2021-03-19

Description of changes
Adds https://github.com/horriblename/hyprgrass and its dependency https://github.com/WayfireWM/wf-touch
Things done

Built on platform(s)

[x] 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

[x] Fits CONTRIBUTING.md.

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

Rebased and added nix-update-script

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

3 packages built:

hyprlandPlugins.hyprgrass
wf-touch
wf-touch.dev


Add CI check for uncommitted migrations

Fixes

Fixes #571  by @sarayourfriend
Description

Adds a new check to verify there are no uncommitted migrations in the PR.
Testing Instructions

Verify that the test commit (43c8c2c581b7d44a2a80829d0fb0782cae2ddd57) introduces uncommitted migrations and that the CI fails for that commit.
Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[N/A] I added or updated tests for the changes I made (if applicable).
[x] I added or updated documentation (if applicable).
[N/A] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

It looks like the most recent CI run failed because it was unable to run the just command, not because of an uncommitted migration thinking

Yes, so far it still hasn't run correctly. I only undrafted this so I could get the CI to run, please ignore for now!

Yes, so far it still hasn't run correctly. I only undrafted this so I could get the CI to run, please ignore for now!

Oh got it, my bad! I didn't realize/remember CI doesn't run on drafts

Seems like the TTY value in the docker-compose won't work for CI :thinking: Why does it work for running the tests?

This run shows it working to pass when there are no uncommitted migrations: https://github.com/WordPress/openverse-api/runs/5680076354
The run was a mistake but at least it proves that it works :slightly_smiling_face:
The next run will show what happens when it should break.

@AetherUnbound @obulat @stacimc this is ready for review now.
You can see that the workflow correctly fails when there are uncommitted migrations: https://github.com/WordPress/openverse-api/runs/5680410997?check_suite_focus=true
And passes when a new migration is added: https://github.com/WordPress/openverse-api/runs/5680076354


ruby version update

Updated ruby version in all files.

Thanks so much... I believe I've made the changes you requested.


Taffybar 1.0.0 broken in master

Issue description
The taffybar package in nixpkgs master cannot build.
Steps to reproduce

Checkout nixpkgs.
nix-env -f . -iA taffybar

installing 'taffybar-with-packages'
these derivations will be built:
  /nix/store/nkbrsnz01lp97i60m59bzrcjqvivacph-gtk-traymanager-1.0.0.drv
  /nix/store/1lkw0v0r6wzl3q0anrz65ysmmgkhmzbm-taffybar-1.0.0.drv
  /nix/store/dk2q2i5h00122pwv96zkx35xid7b910g-ghc-8.2.2-with-packages.drv
  /nix/store/4xhbgnvqcqx6b0bb6q8p89dzgmzqnsyq-taffybar-with-packages.drv
building '/nix/store/nkbrsnz01lp97i60m59bzrcjqvivacph-gtk-traymanager-1.0.0.drv'...
setupCompilerEnvironmentPhase
Build with /nix/store/2pdyyxb4dzhrbpyhq57rwnn8nahahr9f-ghc-8.2.2.
unpacking sources
unpacking source archive /nix/store/4sjcq33a0ki2q8jarlmnx6f7p5r2f818-gtk-traymanager-1.0.0.tar.gz
source root is gtk-traymanager-1.0.0
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file gtk-traymanager-1.0.0/src/Graphics/UI/Gtk/Misc/TrayManager.hs
patching sources
compileBuildDriverPhase
setupCompileFlags: -package-db=/tmp/nix-build-gtk-traymanager-1.0.0.drv-0/package.conf.d -j1 -threaded
[1 of 1] Compiling Main             ( Setup.hs, /tmp/nix-build-gtk-traymanager-1.0.0.drv-0/Main.o )
Linking Setup ...
configuring
configureFlags: --verbose --prefix=/nix/store/ckz4g6akmkfsa2wji1zzd5lm1cbcyb6v-gtk-traymanager-1.0.0 --libdir=$prefix/lib/$compiler --libsubdir=$pkgid --docdir=/nix/store/zh97vhmccq3nzbgv92jdin1q16ak6xis-gtk-traymanager-1.0.0-doc/share/doc --with-gcc=gcc --package-db=/tmp/nix-build-gtk-traymanager-1.0.0.drv-0/package.conf.d --ghc-option=-j1 --disable-split-objs --enable-library-profiling --profiling-detail=all-functions --disable-profiling --enable-shared --disable-coverage --disable-executable-dynamic --enable-tests --enable-library-vanilla --enable-library-for-ghci --ghc-option=-split-sections --extra-lib-dirs=/nix/store/s8c50k081m5xdc2lxz0dwimsnm74rlnb-ncurses-6.1/lib --extra-lib-dirs=/nix/store/7fd1hqfrw1w0csfiv3sic09dhcszgbcc-gmp-6.1.2/lib --extra-lib-dirs=/nix/store/s8c50k081m5xdc2lxz0dwimsnm74rlnb-ncurses-6.1/lib --extra-include-dirs=/nix/store/gdlda7gxf1iwg6j0b4m40mg8w4gi2rmw-freetype-2.7.1-dev/include --extra-lib-dirs=/nix/store/gdlda7gxf1iwg6j0b4m40mg8w4gi2rmw-freetype-2.7.1-dev/lib --extra-include-dirs=/nix/store/spxwrxnsf28sq5gdp42xvqac7psvlqya-zlib-1.2.11-dev/include --extra-lib-dirs=/nix/store/spxwrxnsf28sq5gdp42xvqac7psvlqya-zlib-1.2.11-dev/lib --extra-lib-dirs=/nix/store/sghbqqxllij185b0n3i1ckk30yyjng14-zlib-1.2.11/lib --extra-include-dirs=/nix/store/qh7vxajagv1x0q2xzi0bw70s1gscaqb1-bzip2-<IP_ADDRESS>.1-dev/include --extra-lib-dirs=/nix/store/qh7vxajagv1x0q2xzi0bw70s1gscaqb1-bzip2-<IP_ADDRESS>.1-dev/lib --extra-lib-dirs=/nix/store/khz209lcxylk55hy1qqvk8r8jxjpg01x-bzip2-<IP_ADDRESS>.1/lib --extra-include-dirs=/nix/store/k0k1pv36m1himk885kjl7hll8l9nqrmk-libpng-apng-1.6.34-dev/include --extra-lib-dirs=/nix/store/k0k1pv36m1himk885kjl7hll8l9nqrmk-libpng-apng-1.6.34-dev/lib --extra-lib-dirs=/nix/store/04mbknfbjfg0gl7ha7ybmc3nvl7jc1dk-libpng-apng-1.6.34/lib --extra-lib-dirs=/nix/store/vy2vddqwh19nrfnpwlcn3v0gwkjw938m-freetype-2.7.1/lib --extra-include-dirs=/nix/store/brlpfzip5xgm4pgc4nr2rsxc3dv6pggr-fontconfig-2.12.1-dev/include --extra-lib-dirs=/nix/store/brlpfzip5xgm4pgc4nr2rsxc3dv6pggr-fontconfig-2.12.1-dev/lib --extra-lib-dirs=/nix/store/j4f6mgx0gyr9ajqh6w39pfin0f2iy8fz-fontconfig-2.12.1-lib/lib --extra-include-dirs=/nix/store/vfy9c0mdlzkjkrav5bn35kiwaixaaqhg-xproto-7.0.31/include --extra-lib-dirs=/nix/store/vfy9c0mdlzkjkrav5bn35kiwaixaaqhg-xproto-7.0.31/lib --extra-include-dirs=/nix/store/l5kbz6b54kfsjdica384a3534d3hh0l5-libX11-1.6.5-dev/include --extra-lib-dirs=/nix/store/l5kbz6b54kfsjdica384a3534d3hh0l5-libX11-1.6.5-dev/lib --extra-include-dirs=/nix/store/7yqwvihjl6c8vj99nd7m26jjj32pfkci-libxcb-1.12-dev/include --extra-lib-dirs=/nix/store/7yqwvihjl6c8vj99nd7m26jjj32pfkci-libxcb-1.12-dev/lib --extra-lib-dirs=/nix/store/g4yvi8gwm8rzmpz1iv434vijn3dxr9lq-libxcb-1.12/lib --extra-include-dirs=/nix/store/qmkyisx58n3xqg9lqwa6qvyzzw3vpszn-kbproto-1.0.7/include --extra-lib-dirs=/nix/store/qmkyisx58n3xqg9lqwa6qvyzzw3vpszn-kbproto-1.0.7/lib --extra-lib-dirs=/nix/store/m991w0ib2x6sdc67favv0nmavgy7bghh-libX11-1.6.5/lib --extra-include-dirs=/nix/store/2l0l7zb5mc9shs5jjbblcw5bmwwcjw1x-libXt-1.1.5-dev/include --extra-lib-dirs=/nix/store/2l0l7zb5mc9shs5jjbblcw5bmwwcjw1x-libXt-1.1.5-dev/lib --extra-include-dirs=/nix/store/sx2c626g9ln55304rcqyh46vnz8b5w2v-libSM-1.2.2-dev/include --extra-lib-dirs=/nix/store/sx2c626g9ln55304rcqyh46vnz8b5w2v-libSM-1.2.2-dev/lib --extra-include-dirs=/nix/store/nn97d4zpy5dz7krhh1gqyndzi8bb9yi8-libICE-1.0.9-dev/include --extra-lib-dirs=/nix/store/nn97d4zpy5dz7krhh1gqyndzi8bb9yi8-libICE-1.0.9-dev/lib --extra-lib-dirs=/nix/store/xnfxlm115qfiskxvhy6v5dr7gxnjj85y-libICE-1.0.9/lib --extra-lib-dirs=/nix/store/wlgijr55nyy5dl5fklrjvn0n3vcsh0if-libSM-1.2.2/lib --extra-lib-dirs=/nix/store/0963byncgdnmdbbddwww62f0qxagwkcn-libXt-1.1.5/lib --extra-include-dirs=/nix/store/4zjy7ks07blr9j1i9hzlxx4zcgzhifr2-libXft-2.3.2-dev/include --extra-lib-dirs=/nix/store/4zjy7ks07blr9j1i9hzlxx4zcgzhifr2-libXft-2.3.2-dev/lib --extra-include-dirs=/nix/store/3drzd32ig5gbn2plvfvnivjpbbna2if3-libXrender-0.9.10-dev/include --extra-lib-dirs=/nix/store/3drzd32ig5gbn2plvfvnivjpbbna2if3-libXrender-0.9.10-dev/lib --extra-include-dirs=/nix/store/kjlml6wgbpyczf2x6yqd1k4hpp8dqbfl-renderproto-0.11.1/include --extra-lib-dirs=/nix/store/kjlml6wgbpyczf2x6yqd1k4hpp8dqbfl-renderproto-0.11.1/lib --extra-include-dirs=/nix/store/kjlml6wgbpyczf2x6yqd1k4hpp8dqbfl-renderproto-0.11.1/include --extra-lib-dirs=/nix/store/kjlml6wgbpyczf2x6yqd1k4hpp8dqbfl-renderproto-0.11.1/lib --extra-lib-dirs=/nix/store/rahr8914mspchf6lg2zcnx095k47jmni-libXrender-0.9.10/lib --extra-lib-dirs=/nix/store/4gac2i1wi7g3a4icdm25sxcmm32gczmb-libXft-2.3.2/lib --extra-include-dirs=/nix/store/3lzy99xfv5vv39wb468x0chqy5qk8w9g-libXext-1.3.3-dev/include --extra-lib-dirs=/nix/store/3lzy99xfv5vv39wb468x0chqy5qk8w9g-libXext-1.3.3-dev/lib --extra-include-dirs=/nix/store/v0jdxxgj2la1px6jgnr0jvw378p04zka-libXau-1.0.8-dev/include --extra-lib-dirs=/nix/store/v0jdxxgj2la1px6jgnr0jvw378p04zka-libXau-1.0.8-dev/lib --extra-lib-dirs=/nix/store/2prgw4xa4q9j3sww0psh265cbfqdhf9r-libXau-1.0.8/lib --extra-include-dirs=/nix/store/aqivg8wqhsljjw0n5yw73p3swi2fr6x5-xextproto-7.3.0/include --extra-lib-dirs=/nix/store/aqivg8wqhsljjw0n5yw73p3swi2fr6x5-xextproto-7.3.0/lib --extra-lib-dirs=/nix/store/nh74k3kzdn4dlxgcaqx4if429ayza890-libXext-1.3.3/lib
Configuring gtk-traymanager-1.0.0...
Dependency base >3 && <5: using base-<IP_ADDRESS>
Dependency glib >=0.12.1 && <0.15: using glib-<IP_ADDRESS>
Dependency gtk3 -any: using gtk3-0.14.8
CallStack (from HasCallStack):
  die', called at libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:1507:37 in Cabal-<IP_ADDRESS>:Distribution.Simple.Configure
  configurePkgconfigPackages, called at libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:595:7 in Cabal-<IP_ADDRESS>:Distribution.Simple.Configure
  configure, called at libraries/Cabal/Cabal/Distribution/Simple.hs:570:20 in Cabal-<IP_ADDRESS>:Distribution.Simple
  confHook, called at libraries/Cabal/Cabal/Distribution/Simple/UserHooks.hs:67:5 in Cabal-<IP_ADDRESS>:Distribution.Simple.UserHooks
  configureAction, called at libraries/Cabal/Cabal/Distribution/Simple.hs:174:19 in Cabal-<IP_ADDRESS>:Distribution.Simple
  defaultMainHelper, called at libraries/Cabal/Cabal/Distribution/Simple.hs:119:27 in Cabal-<IP_ADDRESS>:Distribution.Simple
  defaultMain, called at Setup.hs:2:8 in main:Main
Setup: The pkg-config package 'gtk+-3.0' is required but it could not be
found.
builder for '/nix/store/nkbrsnz01lp97i60m59bzrcjqvivacph-gtk-traymanager-1.0.0.drv' failed with exit code 1
cannot build derivation '/nix/store/dk2q2i5h00122pwv96zkx35xid7b910g-ghc-8.2.2-with-packages.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/4xhbgnvqcqx6b0bb6q8p89dzgmzqnsyq-taffybar-with-packages.drv': 1 dependencies couldn't be built
error: build of '/nix/store/4xhbgnvqcqx6b0bb6q8p89dzgmzqnsyq-taffybar-with-packages.drv' failed

Technical details

system: "x86_64-linux"
host os: Linux 4.14.32, NixOS, 18.03.131802.4b4bbce199d (Impala)
multi-user?: yes
sandbox: no
version: nix-env (Nix) 2.0
channels(root): "nixos-18.03.131802.4b4bbce199d"
channels(judson): "nixpkgs-18.09pre134727.d0d05024d10"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

With this change to pkgs/development/haskell-modules/hackage-packages.nix:
   "gtk-traymanager" = callPackage
-    ({ mkDerivation, base, glib, gtk3, x11 }:
+    ({ mkDerivation, base, glib, gtk3, x11, gnome3 }:
      mkDerivation {
        pname = "gtk-traymanager";
        version = "1.0.0";
        sha256 = "1sg2f8pmnh2xrnra8dx46q9jfy32dlbrmk2hamam8g3i5qsvd0f7";
        libraryHaskellDepends = [ base glib gtk3 ];
-       libraryPkgconfigDepends = [ x11 ];
+       libraryPkgconfigDepends = [ x11 gnome3.gtk ];
        homepage = "http://github.com/travitch/gtk-traymanager";

I get https://gist.github.com/35dc774aadab370cf57733946325d94c which is more promising, but I can't get past the build errors.

You can use the top two commits from here as a workaround:
https://github.com/averelld/nixpkgs/commits/taffybar-fixes
I didn't make a PR (anyone feel free), because of the auto-generated hackage-packages.nix, but there are several tiny problems:

gtk-traymanager on hackage was probably manually uploaded, it is simply missing an include from the corresponding git repo (and some whitespace errors), that is the patch file
there are deprecation-warnings which become errors (disabled via patch)
gtk3 is needed as system-package for pkg-config and the identically-named haskell package (see derivation changes with "system-gtk3")
taffybar needs a newer dbus (1_0_1)
taffybar has haddock errors (the comments need to precede the parameters directly), so i just disable haddock

However, this taffybar binary is tested and works :)

Ping @peti

You can do something like
  taffybar = ((overrideCabal super.taffybar (drv: {
    libraryPkgconfigDepends = [ pkgs.gtk3 ];
  })).overrideScope (self: super: {
    dbus = self.dbus_1_0_1;
  }));

in pkgs/development/haskell-modules/configuration-common.nix. Maybe keep the doJailbreak.

Thanks @averelld ! I've got a build of Taffybar now... I like that I can get it on two monitors. I wish I could figure out how to make the text a bit more legible though...

No problem. For reference, I have updated the branch with the above suggestions, thanks @jtojnar , that is easier, and good to know.
Regarding legibility, apparently they use css now instead of the old rc, so maybe try putting this default in your ~/.config/taffybar/ and adjusting the font(size).

Does someone has a solution using overlays ?
I am doing something like this (or variant of):
  haskellPackages = super.haskellPackages.override {
    overrides =  hpkgs: _hpkgs: {
      # vector-builder = hlib.dontCheck(hlib.dontHaddock(_hpkgs.vector-builder.override {}));
      taffybar = hlib.dontHaddock (hlib.doJailbreak _hpkgs.taffybar);
      taffybar_1 =((hlib.overrideCabal _hpkgs.taffybar (drv: {
       libraryPkgconfigDepends = [ self.gtk3 ];
     })).overrideScope (self: super: {
       dbus = self.dbus_1_0_1;
     }));
    };
  };

I can't get over the gtk3+ error:
Setup: The pkg-config package 'gtk+-3.0' is required but it could not be

At the configuration step of the gtk-traymanager

Oh sorry I didn't realize there were 2 packages involved. Will have another try later on.

@PierreR it should work with the let declaration. Otherwise you would also need to make pkgs.taffybarrefer to taffybar_1.

@averelld is it your plan now to issue a PR for this? If not, I'll try to cherry-pick into something.

This issue should not be closed. Taffybar is still broken in nixpkgs, which does not yet have the latest taffybar or gtk-traymanager versions. If the best solution is indeed what @averelld proposes and to wait until the hackage packages are updated, then fine. But this issue is still open until that happens.

@johnchandlerburnham The issue was fixed on master branch. Generally, issues are closed once a fix is merged into a source code repository, they do not wait for a new release (or in our case channel bump.

@jtojnar That's reasonable. When do you think this fix will make it into a channel bump?

For info, there is a memory leak in taffybar-1.0.1. The best would be to wait for 1.0.2 before pushing the fix to 18.03 but it currently doesn't build in master because of a dependency failure (see https://github.com/NixOS/nixpkgs/issues/37724)

More info: taffybar-1.0.2 is also currently broken in nixpkgs due to https://github.com/NixOS/nixpkgs/issues/37724